-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Regression in type inference - critical for sangria-graphl ecosystem #16471
Labels
Milestone
Comments
WojciechMazur
added
itype:bug
area:typer
regression
This worked in a previous version but doesn't anymore
area:infer
labels
Dec 6, 2022
smarter
added a commit
to dotty-staging/dotty
that referenced
this issue
Dec 13, 2022
This regressed in 50eb0e9 when `current.ensureNonCyclic` was incorrectly replaced by `validBoundsFor` which operates on `this`, not `current`. This isn't the first time we make this error (cf a8641c5), maybe we should refactor OrderingConstraint so that operations on `current` are done in the companion object where `this` isn't accessible. Fixes scala#16471.
smarter
added a commit
to dotty-staging/dotty
that referenced
this issue
Dec 13, 2022
This regressed in 50eb0e9 when `current.ensureNonCyclic` was incorrectly replaced by `validBoundsFor` which operates on `this`, not `current`. This isn't the first time we make this error (cf a8641c5), maybe we should refactor OrderingConstraint so that operations on `current` are done in the companion object where `this` isn't accessible. Fixes scala#16471.
smarter
added a commit
to dotty-staging/dotty
that referenced
this issue
Dec 13, 2022
This regressed in 50eb0e9 when `current.ensureNonCyclic` was incorrectly replaced by `validBoundsFor` which operates on `this`, not `current`. This isn't the first time we make this error (cf a8641c5), maybe we should refactor OrderingConstraint so that operations on `current` are done in the companion object where `this` isn't accessible. Fixes scala#16471.
smarter
added a commit
to dotty-staging/dotty
that referenced
this issue
Dec 14, 2022
This regressed in 50eb0e9 when `current.ensureNonCyclic` was incorrectly replaced by `validBoundsFor` which operates on `this`, not `current`. This isn't the first time we make this error (cf a8641c5), maybe we should refactor OrderingConstraint so that operations on `current` are done in the companion object where `this` isn't accessible. Fixes scala#16471. Note that the test case from this issue couldn't be added because it fails `-Ycheck:typer`, but this was also the case before the regression. This is now tracked by scala#16524.
odersky
added a commit
that referenced
this issue
Dec 14, 2022
This regressed in 50eb0e9 when `current.ensureNonCyclic` was incorrectly replaced by `validBoundsFor` which operates on `this`, not `current`. This isn't the first time we make this error (cf a8641c5), maybe we should refactor OrderingConstraint so that operations on `current` are done in the companion object where `this` isn't accessible. Fixes #16471. Note that the test case from this issue couldn't be added because it fails `-Ycheck:typer`, but this was also the case before the regression. This is now tracked by #16524.
little-inferno
pushed a commit
to little-inferno/dotty
that referenced
this issue
Jan 25, 2023
This regressed in 50eb0e9 when `current.ensureNonCyclic` was incorrectly replaced by `validBoundsFor` which operates on `this`, not `current`. This isn't the first time we make this error (cf a8641c5), maybe we should refactor OrderingConstraint so that operations on `current` are done in the companion object where `this` isn't accessible. Fixes scala#16471. Note that the test case from this issue couldn't be added because it fails `-Ycheck:typer`, but this was also the case before the regression. This is now tracked by scala#16524.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Based on the failures in two Open CB projects:
Sangria relies on type inference when defining
Argument
types as they might have complex, tagged types. Due to the regression compiler needs hints about the result type. Otherwise it is not able to resolve itCompiler version
3.3.0-RC1-bin-20221205-5cf8a58-NIGHTLY
Bisect points to 3d4275d
Minimized code
Output
Expectation
Should compile
The text was updated successfully, but these errors were encountered: