Skip to content

[Type checker] Classes don't need backing properties to create their implicit constructors #26239

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 3 commits into from
Jul 19, 2019

Conversation

DougGregor
Copy link
Member

Fixes a crash caused by an undiagnosed cycle, rdar://problem/52679284.

@DougGregor
Copy link
Member Author

@swift-ci please smoke test and merge

This was fixed by pull request swiftlang#26174, but the test case there was
specific to property wrappers, while the fix also addresses issues
with other ambiguity name lookups such as protocol names in an
inheritance clause.
…implicit constructors

Fixes a crash caused by an undiagnosed cycle, rdar://problem/52679284.
Recent improvements in the laziness of the type checker mean that we
weren't guaranteed to get the backing storage property always
synthesized for a wrapped (static) property. Make sure that we create
the backing storage property when walking a source file.
@DougGregor DougGregor force-pushed the property-wrappers-rdar52679284 branch from f57c43d to 10680e4 Compare July 19, 2019 16:07
@DougGregor
Copy link
Member Author

@swift-ci please smoke test and merge

1 similar comment
@DougGregor
Copy link
Member Author

@swift-ci please smoke test and merge

@DougGregor
Copy link
Member Author

@swift-ci please test source compatibility

@swift-ci swift-ci merged commit 8c476c2 into swiftlang:master Jul 19, 2019
@DougGregor DougGregor deleted the property-wrappers-rdar52679284 branch July 19, 2019 18:35
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