Skip to content

Fix #8431 (Make HKT GADT constraints actually work) #8522

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
Mar 26, 2020

Conversation

abgruszecki
Copy link
Contributor

@abgruszecki abgruszecki commented Mar 11, 2020

Fixes #8431.

@smarter this one is ready to go! Going commit-by-commit will help. It turns out that we didn't actually need to care about SI-2712, since:

  1. the problematic function is appOK
  2. which is a nested function of canInstantiate
  3. which is only entered with the RHS tycon, _if_the rhs tycon is a non-instantiated type variable

Fix gadt-uninjectivity test, as it wasn't clear what it was actually
testing.
@abgruszecki abgruszecki marked this pull request as ready for review March 23, 2020 11:35
@abgruszecki abgruszecki requested a review from smarter March 23, 2020 11:46
@abgruszecki abgruszecki changed the title WIP: Fix #8431 Fix #8431 (Make HKT GADT constraints actually work) Mar 23, 2020
@smarter smarter merged commit a324502 into scala:master Mar 26, 2020
@smarter smarter deleted the fix-#8431 branch March 26, 2020 18:02
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.

GADT bounds for higher-kinded variables do not appear to work
2 participants