Skip to content

[5.1 08-28] IRGen: Save the current generic signature before mangling an opaque type decl #27023

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

Conversation

aschwaighofer
Copy link
Contributor

It comes with its own generic signature.

Explanation: We crash generating the mangling for an opaque type decl.

Scope of Issue: Affects code that uses opaque result types.
The compiler will crash.

Risk: Low. We cache and restore a generic signature before mangling opaque type
decls which will introduce their own generic signature.

Review: Joe Groff

Testing: Swift regression test added.

rdar://54824119

… an opaque type decl

It comes with its own generic signature.

Explanation: We crash generating the mangling for an opaque type decl.

Scope of Issue: Affects  code that uses opaque result types.
                The compiler will crash.

Risk: Low. We cache and restore a generic signature before mangling opaque type
     decls which will introduce their own generic signature.

Review: Joe Groff

Testing: Swift regression test added.

rdar://54824119
@aschwaighofer aschwaighofer requested a review from a team as a code owner September 4, 2019 18:58
@aschwaighofer
Copy link
Contributor Author

@swift-ci Please test

@airspeedswift airspeedswift merged commit ae392b2 into swiftlang:swift-5.1-branch-08-28-2019 Sep 9, 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.

2 participants