Skip to content

Handle non-inout Swift type specifiers#1460

Open
erichoracek wants to merge 1 commit into
masterfrom
dev/eh/sourcery-swift-type-specifiers
Open

Handle non-inout Swift type specifiers#1460
erichoracek wants to merge 1 commit into
masterfrom
dev/eh/sourcery-swift-type-specifiers

Conversation

@erichoracek

Copy link
Copy Markdown
Collaborator

Summary

  • Stop asserting when SwiftSyntax represents non-inout type specifiers on attributed types.
  • Preserve existing inout detection while allowing modern Swift specifiers such as sending, isolated, and consuming.
  • Add parser coverage for those specifiers.

Validation

  • env SWIFT_DISABLE_SANDBOX=1 swift test --filter SourceryLibTests.FileParserMethodsSpec/FileParser__parseMethod__extracts_methods_with_non_inout_type_specifiers (builds; Quick filter reports 0 executed examples)
  • Ran local Sourcery against ../superassistant package sources: 16,592 types across 4,741 files, both template passes completed
  • Compared all five generated ../superassistant outputs against checked-in files; no diffs
  • git diff --check

@erichoracek erichoracek changed the title [codex] Handle non-inout Swift type specifiers Handle non-inout Swift type specifiers May 5, 2026
@erichoracek erichoracek marked this pull request as ready for review May 5, 2026 16:23
@krzysztofzablocki

Copy link
Copy Markdown
Owner

probably need to update fixtures

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.

2 participants