Async database accesses no longer require Sendable closures. #1732
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request makes some apps stop compiling, and was reverted in b48a56a. For more information, see https://hachyderm.io/@groue/114054339905066075 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request enhances asynchronous APIs by allowing some non-sendable value to be captured by database access closures without compiler error or warning.
It addresses the feature request by @layoutSubviews expressed at https://mastodon.social/@layoutSubviews/114032891799577133.
Applications that use the Swift 5 language mode may have to enable the
RegionBasedIsolationupcoming feature in order to profit from the enhancement.