Skip to content

IRGen: Correctly indicate non-key same-typed generic parameters. #15984

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 3 commits into from
Apr 17, 2018

Conversation

jckarter
Copy link
Contributor

@jckarter jckarter commented Apr 17, 2018

The correct query here is whether the generic parameter is canonical within its generic signature, not whether it's concrete.

(Note that this includes the patches from #15960, since without that fix this ends up crashing in IRGen elsewhere.)

…redRequirements`.

Fixes a bug where having two generic params same-typed together would lead to crashes in IRGen, and maybe other places, that only expect to deal with canonical params.
The correct query here is whether the generic parameter is canonical within its generic signature, not whether it's concrete.
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@jckarter
Copy link
Contributor Author

@swift-ci Please test source compatibility

@jckarter jckarter requested a review from DougGregor April 17, 2018 19:41
@slavapestov
Copy link
Contributor

Looks good, but an execution test would be nice too!

@jckarter
Copy link
Contributor Author

@slavapestov I've got an execution test coming along with the bug I'm really trying to fix.

@jckarter jckarter merged commit c4121c7 into swiftlang:master Apr 17, 2018
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.

3 participants