Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for cases of a reassignment of a variable #392

Merged
merged 1 commit into from
Mar 27, 2024

Conversation

ericwb
Copy link
Contributor

@ericwb ericwb commented Mar 27, 2024

It is possible for a variable to be used multiple times and even with multiple types prior to its use in the function call. This didn't work because the left hand side of the assignment would be resolved into its complete fully qualified function name.

However, it's also important to keep track of the identifier name in the symbol table in case it is reused. That way the value is properly overwritten.

It is possible for a variable to be used multiple times and even
with multiple types prior to its use in the function call. This
didn't work because the left hand side of the assignment would
be resolved into its complete fully qualified function name.

However, it's also important to keep track of the identifier
name in the symbol table in case it is reused. That way the
value is properly overwritten.

Signed-off-by: Eric Brown <eric.brown@securesauce.dev>
@ericwb ericwb merged commit 2dbd093 into securesauce:main Mar 27, 2024
7 checks passed
@ericwb ericwb deleted the double_assign branch March 27, 2024 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant