Skip to content

Update SE-0365 to discuss source compatibility implications#1819

Closed
calda wants to merge 1 commit intoswiftlang:mainfrom
calda:cal--SE-0365-discuss-source-breakage
Closed

Update SE-0365 to discuss source compatibility implications#1819
calda wants to merge 1 commit intoswiftlang:mainfrom
calda:cal--SE-0365-discuss-source-breakage

Conversation

@calda
Copy link
Copy Markdown
Contributor

@calda calda commented Oct 22, 2022

This PR updates SE-0365 to discuss its implications for source compatibility.

When landing the implementation, we discovered that it's actually source-breaking. This is because there is a bug in Swift 5.7 where implicit self is unexpectedly permitted in non-escaping closures that capture self weakly. This means that this proposal is source-breaking, and can't be enabled until Swift 6. The proposal body now discusses this, and defines changes that will made in Swift 5 mode in preparation for a source-break in Swift 6.

@calda
Copy link
Copy Markdown
Contributor Author

calda commented Oct 22, 2022

This is a follow-up to the discussion here: swiftlang/swift#61520 (comment)

@calda
Copy link
Copy Markdown
Contributor Author

calda commented Oct 31, 2022

Closing since we found an approach for implementing this in Swift 5 mode: swiftlang/swift#61520 (comment)

@calda calda closed this Oct 31, 2022
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