[BUG] Warning when using args as the name of a function argument

[lens0021]

Describe the bug
If you use args as the name of an argument, a warning would be printed when running the bash script.

To Reproduce

$ amber-master eval 'fun fun1(args: [Text]): Null {echo "Hello"} main(args) {fun1(args)}'
main: line 6: fun1__0_v0: args: readonly variable
main: line 6: local: args: readonly variable
Hello

Expected behavior
No warning printed. Like when you use args1 as the name, then:

$ amber-master eval 'fun fun1(args1: [Text]): Null {echo "Hello"} main(args) {fun1(args)}'
Hello

Additional context
echo 'fun fun1(args: [Text]): Null {echo "Hello"} main(args) {fun1(args)}' | amber-master build -:

#!/usr/bin/env bash
# Written in [Amber](https://amber-lang.com/)
# version: 0.3.5-alpha
# date: 2024-12-12 23:51:55
fun1__0_v0() {
    local args=("${!1}")
    echo "Hello"
}
declare -r args=("$0" "$@")
fun1__0_v0 args[@]
__AF_fun10_v0__1_57="$__AF_fun10_v0"
echo "$__AF_fun10_v0__1_57" >/dev/null 2>&1

It seems args is declared twice.

[lens0021]

Therefore,

amber/src/std/env.ab

Line 110 in 82817af

pub fun printf(format: Text, args: [Text] = [""]): Null {

prints the warning. Isn't it happened to anyone than me?

[Mte90]

I don't know if #630 will fix it

[hdwalters]

Also:

$ echo -e 'fun fun1(args: [Text]): Null {echo "Hello"}\n main(args) {fun1(args)}' | amber-master build - | bash

Wow, that's a convoluted way of running an Amber fragment. Wouldn't it be simpler to use amber eval?

[lens0021]

I'm not yet familiar with the new sub commands enough 😅

[lens0021]

(*edited)

[hdwalters]

Looks like we just need to mangle the variable name args with a global variable ID, so we create something like:

declare -r __args_0=("$0" "$@")