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
This change attempts to improve handleIf behavior.
We introduce implicit kind of vars to express automatically
defined vars that can be handled in a special way.
andWalker.varsToDelete are removed because we're running
all branches in a separate block contexts. No extra
cleanup is required.
Changed code requires to evaluate if statement condition
separately, so we can get variables defined inside it
into the parent block context.
assignWalker type does that.
Fixes#369Fixes#363Fixes#370
Signed-off-by: Iskander Sharipov <quasilyte@gmail.com>
This change attempts to improve handleIf behavior.
We introduce implicit kind of vars to express automatically
defined vars that can be handled in a special way.
andWalker.varsToDelete are removed because we're running
all branches in a separate block contexts. No extra
cleanup is required.
Changed code requires to evaluate if statement condition
separately, so we can get variables defined inside it
into the parent block context.
assignWalker type does that.
Fixes#369Fixes#363Fixes#370
Signed-off-by: Iskander Sharipov <quasilyte@gmail.com>
Code Example
Actual Behavior
No warnings.
Expected Behavior
Warning for undefined property
a
.The problem is, noverify assigns
\Fooo1|\Fooo2
type for$globf
inside a second if body, so we can access both Fooo1 and Fooo2 members there.The text was updated successfully, but these errors were encountered: