7x31/shellcheck
1
0
Fork 0
mirror of https://github.com/koalaman/shellcheck.git synced 2025-10-03 19:29:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix plural form

Simon Brandt
2025-06-05 10:31:50 +02:00
parent ae02c453e2
commit f54683e4c9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
SC2034.md

@@ -37,9 +37,9 @@ export "$name"; eval "echo $name"
declare -n name; echo "$name" declare -n name; echo "$name"
``` ```
This is an intentional design decision and not a bug. If you have variables that will not have direct references, consider using an associative array in bash, or just [[Ignore]] the warning. This is an intentional design decision and not a bug. If you have variables that will not have direct references, consider using an associative array in bash, or just [[ignore]] the warning.
Tracking indirect references is a common problem for compilers and static analysis tool, and it is known to be unsolvable in the most general case. There are two ways to handle unresolved indirections (which in a realistic program will essentially be all of them): Tracking indirect references is a common problem for compilers and static analysis tools, and it is known to be unsolvable in the most general case. There are two ways to handle unresolved indirections (which in a realistic program will essentially be all of them):
* Avoid false positives by assuming all variables may potentially be used (disable all unused variable warnings) * Avoid false positives by assuming all variables may potentially be used (disable all unused variable warnings)
* Keep true positives by allowing some false positives (emit unused variable warnings that may be incorrect) * Keep true positives by allowing some false positives (emit unused variable warnings that may be incorrect)