Marker protocols and conditional conformances #36069
Merged
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
This improves source compatibility in cases where a marker protocol is introduced after-the-fact (e.g., for `Error`), and is safe because there's no runtime component to marker protocols.
|
@swift-ci please smoke test |
… protocols These conditional conformances could not be properly evaluated at runtime, so ban them. We still allow conditional conformances to marker protocols.
DougGregor
force-pushed
the
marker-protocols-conditional-conformances
branch
from
d59ad61 to
618378a
Compare
|
@swift-ci please smoke test |
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.
Introduce two semantic tweaks for marker protocols: