Skip to content
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

[5.10] Fix warnings about retroactive conformances when building swift-syntax 510 with a Swift 6 compiler #2644

Merged

Conversation

ahoppen
Copy link
Member

@ahoppen ahoppen commented May 7, 2024

  • Explanation: When building swift-syntax using a Swift 6 compiler, it emits warnings about retractive conformances. Add conditional compilation conditions to add @retroactive where needed if compiling with a Swift 6 compiler to fix those warnings.
  • Scope: No functionality change. Does not require a new toolchain, will just be a new swift-syntax tag
  • Risk: Low, no functionality change.
  • Testing: Verified that swift-syntax still builds using a Swift 5 and Swift 6 compiler
  • Issue: rdar://127134889
  • Reviewer: @bnbarham

…x 510 with a Swift 6 compiler

- **Explanation**: When building swift-syntax using a Swift 6 compiler, it emits warnings about retractive conformances. Add conditional compilation conditions to add `@retroactive` where needed if compiling with a Swift 6 compiler to fix those warnings.
- **Scope**: No functionality change. Does not require a new toolchain, will just be a new swift-syntax tag
- **Risk**: Low, no functionality change.
- **Testing**: Verified that swift-syntax still builds using a Swift 5 and Swift 6 compiler
- **Issue**: rdar://127134889
- **Reviewer**:  @bnbarham
@ahoppen
Copy link
Member Author

ahoppen commented May 7, 2024

@swift-ci Please test

@ahoppen ahoppen merged commit 303e5c5 into swiftlang:release/5.10 May 7, 2024
3 checks passed
@ahoppen ahoppen deleted the 5.10/fix-retroactive-warnings branch May 7, 2024 16:02
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