Skip to content

Don't allow overloading by opaque types with different constraints. #26097

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

jckarter
Copy link
Contributor

@jckarter jckarter commented Jul 11, 2019

The mangling unfortunately doesn't take the constraints into account, leading to #53122 | rdar://problem/50987172. Changing the mangling at this point is hazardous, so it's probably best to disallow this for now.

Resolves #53122

The mangling unfortunately doesn't take the constraints into account, leading to
SR-10725 | rdar://problem/50987172. Changing the mangling at this point is hazardous, so it's probably best
to disallow this for now.
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@jckarter jckarter requested a review from slavapestov July 11, 2019 22:24
@jckarter jckarter merged commit ccc70b7 into swiftlang:master Jul 17, 2019
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-10725] Result type overload with two opaque result type cause compiler crash
2 participants