Skip to content

Add representation and parser support for the @isolated type attribute #2472

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
Feb 7, 2024

Conversation

rjmccall
Copy link
Contributor

@rjmccall rjmccall commented Feb 5, 2024

No description provided.

@rjmccall
Copy link
Contributor Author

rjmccall commented Feb 5, 2024

@swift-ci Please test

@rjmccall
Copy link
Contributor Author

rjmccall commented Feb 6, 2024

@swift-ci Please test

@rjmccall rjmccall force-pushed the add-isolated-any branch 2 times, most recently from ab536f0 to 2d15f31 Compare February 6, 2024 07:29
@rjmccall rjmccall requested a review from DougGregor as a code owner February 6, 2024 07:29
@rjmccall
Copy link
Contributor Author

rjmccall commented Feb 6, 2024

@swift-ci Please test

@rjmccall
Copy link
Contributor Author

rjmccall commented Feb 6, 2024

@swift-ci Please test Windows platform

@rjmccall rjmccall force-pushed the add-isolated-any branch 2 times, most recently from 4d4e241 to 2873541 Compare February 6, 2024 22:23
@rjmccall
Copy link
Contributor Author

rjmccall commented Feb 6, 2024

@swift-ci Please test

Copy link
Member

@ahoppen ahoppen left a comment

Choose a reason for hiding this comment

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

Thank you! Much simpler as well 👍🏽

@rjmccall
Copy link
Contributor Author

rjmccall commented Feb 6, 2024

@swift-ci Please test Windows

As part of this, I had to update the attribute parser to not recurse into
the full parseType routine since that would attempt to parse attributes
again right after the `@`.  Doing so allows some genuinely bizarre constructs
that we obviously don't want and will reject in semantic analysis anyway.
For `@isolated` specifically, it creates an artificial parsing conflict
with the `isolated` parameter specifier and possible future declaration
modifier, just in case you wanted attributes to apply to your attributes.
@rjmccall
Copy link
Contributor Author

rjmccall commented Feb 7, 2024

@swift-ci Please test

@rjmccall
Copy link
Contributor Author

rjmccall commented Feb 7, 2024

@swift-ci Please test Windows

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.

3 participants