Skip to content

Conversation

@bnbarham
Copy link
Contributor

@bnbarham bnbarham commented Nov 11, 2025

There's a few issues here:

  1. Type specifiers can now have arguments (eg. nonisolated(nonsending))
  2. Some type specifiers can be specified "late", which are currently unhandled
  3. We were using a mix of .same and .continue breaks (.continue for specifiers and .same for attributes)
  4. Attributes were grouped separately to specifiers

Fixes #1081

Copy link
Member

@allevato allevato left a comment

Choose a reason for hiding this comment

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

Thanks!

There's a few issues here:
1. Type specifiers can now have arguments (eg. `nonisolated(nonsending)`)
2. Some type specifiers can be specified "late", which are currently unhandled
3. We were using a mix of `.same` and `.continue` breaks (`.continue` for
   specifiers and `.same` for attributes)
4. Attributes were grouped separately to specifiers

Fixes swiftlang#1081
@bnbarham bnbarham force-pushed the specifiers-with-params branch from 24d2533 to b2091bd Compare November 11, 2025 23:14
@bnbarham bnbarham merged commit f45ca4f into swiftlang:main Nov 11, 2025
53 of 56 checks passed
@bnbarham bnbarham deleted the specifiers-with-params branch November 11, 2025 23:49
ahoppen added a commit to ahoppen/sourcekit-lsp that referenced this pull request Nov 12, 2025
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.

nonisolated(nonsending) is formatted incorrectly

2 participants