Skip to content

Conversation

jckarter
Copy link
Contributor

@jckarter jckarter commented Jun 7, 2016

emitLValue always has to occur in a writeback scope, even if the lvalue isn't formally accessed until later, because some lvalue productions immediately access their parent lvalue expression (namely optional chaining expressions). Fixes rdar://problem/26642478.

@jckarter jckarter force-pushed the emit-lvalue-writeback-scope branch from e7b39da to 77719a5 Compare June 7, 2016 19:51
emitLValue always has to occur in a writeback scope, even if the lvalue isn't formally accessed until later, because some lvalue productions immediately access their parent lvalue expression (namely optional chaining expressions). Fixes rdar://problem/26642478.
@jckarter
Copy link
Contributor Author

jckarter commented Jun 7, 2016

@swift-ci Please test and merge

@swift-ci swift-ci merged commit b4b44c6 into swiftlang:master Jun 7, 2016
@jckarter jckarter deleted the emit-lvalue-writeback-scope branch June 7, 2016 22:35
MaxDesiatov pushed a commit that referenced this pull request Apr 19, 2021
[pull] swiftwasm from main
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.

2 participants