Skip to content

[Serialization] Teach serialization to get a generic signature from opaque types #26586

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
Aug 13, 2019

Conversation

harlanhaskins
Copy link
Contributor

Previously, if we had an XREF to an opaque type, we would fail trying to
get the generic signature from that type.

Fixes rdar://53958358

@harlanhaskins harlanhaskins requested a review from jckarter August 9, 2019 22:47
@harlanhaskins
Copy link
Contributor Author

Trying to make a test case for this now

Copy link
Contributor

@jckarter jckarter left a comment

Choose a reason for hiding this comment

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

Thanks for fixing this!

@harlanhaskins
Copy link
Contributor Author

@swift-ci please smoke test

1 similar comment
@harlanhaskins
Copy link
Contributor Author

@swift-ci please smoke test

Harlan Haskins added 2 commits August 12, 2019 15:08
…YPE_PATH_PIECE

We might have an opaque return type path piece after a generic type
param type, so make sure to emit the XREF entry before the opaque return
type path piece as well.

Fixes rdar://53958358
…paque types

Previously, if we had an XREF to an opaque type, we would fail trying to
get the generic signature from that type.

Fixes rdar://53958358
@harlanhaskins
Copy link
Contributor Author

@swift-ci please smoke test Linux

@harlanhaskins
Copy link
Contributor Author

@swift-ci please smoke test macOS

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