Skip to content

[Concurrency] Do not allow actor isolation violations in function conversions to impact constraint solving. #68685

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

Merged

Conversation

hborla
Copy link
Member

@hborla hborla commented Sep 21, 2023

This is an attempt to steer the constraint system away from needing to reason about actor isolation violations. Being able to determine actor isolation from an already-type-checked expression alone is a desirable property, because it may allow us to enable actor-isolated default arguments and only diagnose violations based on the caller's actor isolation. Concretely, this change will always allow function conversions that add or remove global-actor attributes in the constraint system, and violations are always diagnosed later on in the actor isolation checker. This means that the presence of a function conversion that violates actor isolation cannot impact solution ranking.

@hborla
Copy link
Member Author

hborla commented Sep 21, 2023

@swift-ci please smoke test

@hborla hborla force-pushed the minimize-constraint-system-isolation-checking branch from c01ee96 to 2e9c64d Compare September 22, 2023 02:44
@hborla hborla requested a review from slavapestov as a code owner September 22, 2023 02:44
@hborla
Copy link
Member Author

hborla commented Sep 22, 2023

@swift-ci please smoke test

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