Skip to content

[NCGenerics] allow feature-guarded uses of ~Copyable #69821

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 2 commits into from
Nov 14, 2023

Conversation

kavon
Copy link
Member

@kavon kavon commented Nov 13, 2023

We need to delay the pre-NCGenerics errors about illegal uses of ~Copyable from Parse until Sema. Otherwise, such uses can't appear within a false #if-block.

@kavon kavon force-pushed the ncgenerics-feature-guard-parsing branch 2 times, most recently from 0c09e2e to f7dc938 Compare November 13, 2023 20:29
@kavon
Copy link
Member Author

kavon commented Nov 13, 2023

@swift-ci please smoke test

@kavon kavon enabled auto-merge November 13, 2023 20:31
There are sometimes parsing stuations where we don't want to
emit a parsing error, because of feature guarding. For
example, if a Feature involves new syntax for a type, we
must be able to parse both the true and false sides of an
ifdef guarding that new syntax based on a Feature flag.
We need to delay the pre-NCGenerics errors about
illegal uses of ~Copyable from Parse until Sema.
Otherwise, such uses can't appear within a false
@kavon kavon force-pushed the ncgenerics-feature-guard-parsing branch from f7dc938 to dbd17c5 Compare November 13, 2023 23:52
@kavon
Copy link
Member Author

kavon commented Nov 13, 2023

@swift-ci please smoke test

@kavon kavon merged commit db7a400 into swiftlang:main Nov 14, 2023
@kavon kavon deleted the ncgenerics-feature-guard-parsing branch November 14, 2023 05:38
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.

1 participant