Multiple issues on Bash with `declare -n`

[S4mu3LJ3f]

• My shellcheck version (0.11.0 and "online"):
• The rule's wiki page does not already cover this
• I tried on https://www.shellcheck.net/

Here's a snippet or screenshot that shows the problem:

#!/bin/bash
declare i=0
declare -A arr_123=()
declare -n arr=arr_123

arr+=([${i}]="$i")
echo "${arr[${i}]}"

Here's what shellcheck currently says:

In test.sh line 4:
declare -A arr_123=()
           ^-----^ SC2034 (warning): arr_123 appears unused. Verify use (or export if used externally).

In test.sh line 7:
arr+=([${i}]="$i")
       ^--^ SC2004 (style): $/${} is unnecessary on arithmetic variables.

And when I change to just [i] behavior changes too.

Also I have issue with SC2178 on declare -n that I can't reproduce in test script for now.

In scr line 895:
    declare -n array_inscr="array_inscr_${i}"   # Array was declared with `-a`
               ^---------^ SC2178 (warning): Variable was used as an array but is now assigned a string.

Here's what I wanted or expected to see:

No warnings when used without a reference.

#!/bin/bash
declare i=0
declare -A arr_123=()
#declare -n arr=arr_123

arr_123+=([${i}]="$i")
echo "${arr_123[${i}]}"

[wileyhy]

Hi, One bug per issue, please, would really help with tracking any varying resolutions. Dynamic parameter names can be quite fragile, however. Multiple indexed arrays with synchronized indices can be used for simulating multi-dimensional arrays, depending on your use case. Happy Holidays,

…

On Thu, Dec 25, 2025, 12:56 S4mu3LJ3f ***@***.***> wrote: *S4mu3LJ3f* created an issue (koalaman/shellcheck#3380) <#3380> - Rule Id (if any, e.g. SC1000): - My shellcheck version (0.11.0 and "online"): - The rule's wiki page does not already cover this (e.g. https://shellcheck.net/wiki/SC2086) - I tried on https://www.shellcheck.net/ Here's a snippet or screenshot that shows the problem: #!/bin/bashdeclare i=0declare -A arr_123=()declare -n arr=arr_123 arr+=([${i}]="$i")echo "${arr[${i}]}" Here's what shellcheck currently says: In test.sh line 4: declare -A arr_123=() ^-----^ SC2034 (warning): arr_123 appears unused. Verify use (or export if used externally). In test.sh line 7: arr+=([${i}]="$i") ^--^ SC2004 (style): $/${} is unnecessary on arithmetic variables. And when I change to just [i] behavior changes too. Here's what I wanted or expected to see: No warnings when used without a reference. #!/bin/bashdeclare i=0declare -A arr_123=()#declare -n arr=arr_123 arr_123+=([${i}]="$i")echo "${arr_123[${i}]}" Also I have issue with SC2178 on declare -n that I can't reproduce in test script for now. In scr line 895: declare -n array_inscr="array_inscr_${i}" # Array was declared with `-a` ^---------^ SC2178 (warning): Variable was used as an array but is now assigned a string. — Reply to this email directly, view it on GitHub <#3380>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUF2F22SAPHBF54AUEF6I734DRFPZAVCNFSM6AAAAACQARP2M2VHI2DSMVQWIX3LMV43ASLTON2WKOZTG43DEMZVGQ2DENQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[S4mu3LJ3f]

I assume this is the one bug with declare -n.