Skip to content

Check conformance availability for associated conformances #34651

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

slavapestov
Copy link
Contributor

@slavapestov slavapestov commented Nov 10, 2020

Follow-up to #34565.

Part of rdar://problem/35158274.

@slavapestov slavapestov force-pushed the assoc-conformance-availability branch from 98845ee to 64639c6 Compare November 10, 2020 03:21
Let's point out the associated type with a separate note, so
that we can diagnose other availability failures, such as
deprecation and OS version availability.
This replaces the old exportability check with a call into the
new general conformance availability check entry point.

Part of <rdar://problem/35158274>.
@slavapestov slavapestov force-pushed the assoc-conformance-availability branch from 64639c6 to db394c5 Compare November 10, 2020 04:44
@slavapestov
Copy link
Contributor Author

@swift-ci Please test

@slavapestov
Copy link
Contributor Author

@swift-ci Please test source compatibility

1 similar comment
@slavapestov
Copy link
Contributor Author

@swift-ci Please test source compatibility

@slavapestov
Copy link
Contributor Author

@swift-ci Please test Windows platform

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