[TypeChecker] InferSendableFromCaptures: Infer @Sendable on adjusted types
#72527
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
…e `FunctionType` This method is always called after the type is opened by the solver which means that we never end up with `GenericFunctionType`.
…adjustFunctionTypeForConcurrency`
…nversions None of the diagnostics in MiscDiagnostics make a distinction between sendable or actor-isolated function references which means that we can skip conversions while reaching for a declaration used in an application.
…bers to `adjustFunctionTypeForConcurrency`
|
@swift-ci please test |
hborla
approved these changes
Mar 28, 2024
|
@swift-ci please test |
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.
Previously sendability was inferred directly on an (opened) interface type and
carried over to the "adjusted" type, this creates a problem for some partially
applied references to isolated members because they have to be wrapped in an
autoclosure that would attempt a conversion from i.e.
@Sendableto@MainActortype and be diagnosed an a concurrency issue.
Instead of doing that let's apply inference to the adjusted type, which maintains
original behavior where (opened) interface type is adjusted via
FunctionConversionExprto a type with appropriate concurrency annotations.
Resolves: rdar://119593407