Skip to content

Conversation

@Linyxus
Copy link
Contributor

@Linyxus Linyxus commented Mar 21, 2022

This PR fixes #14726. By calling exclusiveLower before addLess, we can properly propagate GADT upper bounds to lower parameters.

@abgruszecki
Copy link
Contributor

Excellent, great job @Linyxus! This LGTM now, we'll merge if the tests pass.

@abgruszecki abgruszecki enabled auto-merge March 24, 2022 17:09
@Linyxus
Copy link
Contributor Author

Linyxus commented Mar 25, 2022

It seems that the checks are not triggered for the latest commit. Is it possible to run it manually?

@som-snytt
Copy link
Contributor

auto-merge was automatically disabled March 25, 2022 06:05

Head branch was pushed to by a user without write access

@Linyxus
Copy link
Contributor Author

Linyxus commented Mar 25, 2022

It seems that for some reason the results from the run is not reported in the PR. I force pushed to the branch (and squash the two fixing commits into the same one by the way); the checks are running now.

@dwijnand dwijnand merged commit e6a6e30 into scala:main Mar 25, 2022
@Kordyjan Kordyjan added this to the 3.1.3 milestone Aug 1, 2023
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 upper bounds are not properly propagated during unification

5 participants