Sema: Fix crash-on-invalid with 'let' property in protocol [5.1] #25146
Conversation
This file contains hidden or 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
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
slavapestov
force-pushed
the
protocol-requirement-accessor-crash-5.1
branch
from
9c1c3d0 to
e844db1
Compare
|
@swift-ci Please test |
|
Build failed |
The protocol requirement storage declaration might not have accessors created for it if it was incorrectly declared as a 'let' property inside the protocol. There might be other cases where we had failed to synthesize the requirement's accessors, and crash here; this should hopefully make all of those more robust. Fixes <rdar://problem/48994271>.
slavapestov
force-pushed
the
protocol-requirement-accessor-crash-5.1
branch
from
e844db1 to
8ca363b
Compare
|
@swift-ci Please test |
1 similar comment
|
@swift-ci Please test |
|
Build failed |
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.
The protocol requirement storage declaration might not have accessors
created for it if it was incorrectly declared as a 'let' property
inside the protocol.
There might be other cases where we had failed to synthesize the
requirement's accessors, and crash here; this should hopefully make
all of those more robust.
Fixes rdar://problem/48994271.