Skip to content

[CSApply] Don't try to force propagate l-value access in "shallow" mode #15287

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
Mar 16, 2018

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Mar 16, 2018

Some of the expressions call into typeCheckExpressionShallow while trying to
apply solutions, we need to respect the fact that sub-expressions might be
already properly type-checked while propagating l-value access kind.

Resolves: rdar://problem/38309176

@xedin xedin requested a review from rudkx March 16, 2018 01:07
Some of the expressions call into `typeCheckExpressionShallow` while trying to
apply solutions, we need to respect the fact that sub-expressions might be
already properly type-checked while propagating l-value access kind.

Resolves: rdar://problem/38309176
Copy link
Contributor

@rudkx rudkx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, seems reasonable.

@xedin
Copy link
Contributor Author

xedin commented Mar 16, 2018

@swift-ci please smoke test

@xedin
Copy link
Contributor Author

xedin commented Mar 16, 2018

@swift-ci please test source compatibility

@xedin xedin merged commit 4850d54 into swiftlang:master Mar 16, 2018
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