Skip to content

SE-0458: Disambiguate postfix expressions vs. unsafe expressions more generally #79842

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
Mar 8, 2025

Conversation

DougGregor
Copy link
Member

Handle call-vs-tuple and subscript-vs-collection-expr disambiguation using the same "no trivia" rule that we used to disambiguite "unsafe.x" (which we treat as a member access) from "unsafe .x" (which we treat as an unsafe expression with a leading-dot member access).

Fixes rdar://146459104.

… generally

Handle call-vs-tuple and subscript-vs-collection-expr disambiguation using the
same "no trivia" rule that we used to disambiguite "unsafe.x" (which we
treat as a member access) from "unsafe .x" (which we treat as an unsafe
expression with a leading-dot member access).

Fixes rdar://146459104.
@DougGregor
Copy link
Member Author

swiftlang/swift-syntax#3005

@swift-ci please smoke test

@DougGregor DougGregor merged commit b038376 into swiftlang:main Mar 8, 2025
3 checks passed
@DougGregor DougGregor deleted the se-0458-postfix-disambig branch March 8, 2025 02:56
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