You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Detect variables which may be undefined in some code paths #299
That second one is the same as #242, but the first of those examples is different as the analyzer will see that x is defined in the same scope and won't warn and is probably a further enhancement.
I think that first one could actually just be solved by #313 (dataflow analysis recognizing a code path without the variable being defined), so I'll do the naming fixes then close this when those are in.
Activity
jakebailey commentedon Oct 22, 2018
That second one is the same as #242, but the first of those examples is different as the analyzer will see that x is defined in the same scope and won't warn and is probably a further enhancement.
With #298:
MikhailArkhipov commentedon Oct 22, 2018
I'd change message to 'variable is possibly undeclared in some code path'
MikhailArkhipov commentedon Oct 24, 2018
Jake Bailey (@jakebailey) - wrt the message wording
[-]Detect variables referenced before assignment[/-][+]Change unknown variable message[/+]qubitron commentedon Oct 24, 2018
Need to move messages to resources
Remove (analysis), (parser) etc.
[-]Change unknown variable message[/-][+]Detect variables which may be undefined in some code paths[/+]jakebailey commentedon Oct 30, 2018
I think that first one could actually just be solved by #313 (dataflow analysis recognizing a code path without the variable being defined), so I'll do the naming fixes then close this when those are in.
Resource-ify diagnostic messages, rename some codes, remove "(...)" (#…
Resource-ify diagnostic messages, rename some codes, remove "(...)" (m…