Scope assignation returns assigned value #1386
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes an issue in smart contract language where it could be possible for a user to have an atom in a variable.
When assigning a value to a variable, we call
Scope.write_cascade
, this function was returning:ok
. The problem was that we could create a function where the last statement is a assignation, and so the function returns:ok
The fix is to have the same behavior than elixir, the assignation return the assigned value
Type of change
How Has This Been Tested?
Create a simple contract with a function that assign a value in it's last statement
Checklist: