Skip to content

Always use the l-value logic for emitting key path applications #20459

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

Merged
merged 1 commit into from
Nov 9, 2018

Conversation

rjmccall
Copy link
Contributor

@rjmccall rjmccall commented Nov 9, 2018

Not NFC because it also fixes an evaluation order bug (and reorders some less-important stuff): the key-path expression needs to be evaluated immediately during formal evaluation and cannot be delayed until start-of-access.

Not NFC because it also fixes an evaluation order bug (and reorders
some less-important stuff): the key-path expression needs to be
evaluated immediately during formal evaluation and cannot be delayed
until start-of-access.
@rjmccall
Copy link
Contributor Author

rjmccall commented Nov 9, 2018

@swift-ci Please test.

@rjmccall rjmccall requested a review from jckarter November 9, 2018 07:43
@jckarter
Copy link
Contributor

jckarter commented Nov 9, 2018

Makes sense, thanks John!

@rjmccall rjmccall merged commit e741147 into swiftlang:master Nov 9, 2018
@rjmccall rjmccall deleted the key-path-lvalue-emission branch November 9, 2018 17:08
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