-
-
Notifications
You must be signed in to change notification settings - Fork 667
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: return the assigned value in assignments #2773
Merged
HerrCai0907
merged 5 commits into
AssemblyScript:main
from
HerrCai0907:2770-assignment-chain-cause-compatibility-issue
Nov 8, 2023
Merged
fix: return the assigned value in assignments #2773
HerrCai0907
merged 5 commits into
AssemblyScript:main
from
HerrCai0907:2770-assignment-chain-cause-compatibility-issue
Nov 8, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In `makeAssignment`, `valueType` doesn't match witch valueExpr. But there are no actual influence for current generated wasm.
deps: #2772 |
HerrCai0907
force-pushed
the
2770-assignment-chain-cause-compatibility-issue
branch
from
October 17, 2023 09:30
dc9df96
to
f40e4a3
Compare
HerrCai0907
force-pushed
the
2770-assignment-chain-cause-compatibility-issue
branch
from
October 18, 2023 03:22
f40e4a3
to
a18920f
Compare
HerrCai0907
force-pushed
the
2770-assignment-chain-cause-compatibility-issue
branch
from
October 18, 2023 03:39
a18920f
to
b755426
Compare
WDYT @CountBleck @dcodeIO @MaxGraey ? |
ping @CountBleck |
CountBleck
approved these changes
Nov 7, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything seems good here
return this.makeAssignment( | ||
target, | ||
this.convertExpression(valueExpr, valueType, targetType, false, valueExpression), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code was better before, but this is okay.
CountBleck
changed the title
fix: avoid use getInstance in assignment chain
fix: return the assigned value in assignments
Nov 7, 2023
…in-cause-compatibility-issue
HerrCai0907
deleted the
2770-assignment-chain-cause-compatibility-issue
branch
November 8, 2023 03:49
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In TS, assignment chain will assign result to each variable. But in AS, assignment chain will assign result to second variable and assign the value of second variable to the first variable.
It will cause incompatibility problem.
This patch assign result to a temporary local and assign it to each variable.
Fixes #2770.