[6.0][region-isolation] Given a .none #isolation parameter, infer the isolation from the callee rather than the isolated parameter. #74727
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.
Explanation: This PR fixes an issue that affects the usage of functions that use
#isolated
. The specific problem is that when we call such a function without an actual actor (so we go to the main queue), we improperly infer the isolation of the enum.none to be slightly different from the isolation of other parameters.The result is that one can get an isolation mismerge that then results in a "unknown pattern" error.
Radars:
Original PRs:
Risk: Low.
Testing: Added tests to the compiler.
Reviewer: @ktoso