Skip to content

Sema: Reject 'any P' in inheritance clause #41537

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
merged 2 commits into from
Feb 24, 2022

Conversation

slavapestov
Copy link
Contributor

@slavapestov slavapestov commented Feb 24, 2022

This uncovers another issue, where @unchecked Sendable resolves as any Sendable rather than Sendable, so fix that by using the correct TypeResolverContext.

Resolves #56304.

…ontext

Otherwise, '@unchecked Sendable' will wrap the 'Sendable' in an
ExistentalType.
@slavapestov slavapestov requested a review from hborla February 24, 2022 03:31
Copy link
Member

@hborla hborla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Time to start printing any in all diagnostics!

@slavapestov slavapestov force-pushed the ban-any-in-inheritance-clause branch from 7ad6c01 to 250fbf2 Compare February 24, 2022 04:10
@slavapestov
Copy link
Contributor Author

@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.

[SR-13906] Error message is unclear when a type conforms to AnyObject or a composition of it
2 participants