-
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
Possible regression in type inference #15652
Comments
griggt
added
itype:bug
stat:needs triage
Every issue needs to have an "area" and "itype" label
labels
Jul 12, 2022
Can we find out what commit caused this? |
Workaround: def optionalOneOf[T](in: Map[String, NodeParser[T]]): Option[T] This is really what it should have been all along. |
mbovel
added
area:typer
and removed
stat:needs triage
Every issue needs to have an "area" and "itype" label
labels
Jul 12, 2022
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Jul 13, 2022
We sometimes create a dependent parameter reference p.X where `p` is a path with a type that has a wildcard argument, e.g. `P[X >: L <: H].` So far the denotation of `p.X` had as info the bounds with which `X` was declared in `P`. Now it gets the actual parameter bounds instead. Fixes scala#15652 scala#15652 started failing when tuple unpackings started to use `val`s instead of `def`s in scala#14816. That caused dependent class parameter references to be created and uncovered the problem.
Kordyjan
pushed a commit
to dotty-staging/dotty
that referenced
this issue
Jul 26, 2022
We sometimes create a dependent parameter reference p.X where `p` is a path with a type that has a wildcard argument, e.g. `P[X >: L <: H].` So far the denotation of `p.X` had as info the bounds with which `X` was declared in `P`. Now it gets the actual parameter bounds instead. Fixes scala#15652 scala#15652 started failing when tuple unpackings started to use `val`s instead of `def`s in scala#14816. That caused dependent class parameter references to be created and uncovered the problem.
Kordyjan
pushed a commit
to dotty-staging/dotty
that referenced
this issue
Jul 26, 2022
We sometimes create a dependent parameter reference p.X where `p` is a path with a type that has a wildcard argument, e.g. `P[X >: L <: H].` So far the denotation of `p.X` had as info the bounds with which `X` was declared in `P`. Now it gets the actual parameter bounds instead. Fixes scala#15652 scala#15652 started failing when tuple unpackings started to use `val`s instead of `def`s in scala#14816. That caused dependent class parameter references to be created and uncovered the problem.
bishabosha
pushed a commit
to dotty-staging/dotty
that referenced
this issue
Oct 18, 2022
We sometimes create a dependent parameter reference p.X where `p` is a path with a type that has a wildcard argument, e.g. `P[X >: L <: H].` So far the denotation of `p.X` had as info the bounds with which `X` was declared in `P`. Now it gets the actual parameter bounds instead. Fixes scala#15652 scala#15652 started failing when tuple unpackings started to use `val`s instead of `def`s in scala#14816. That caused dependent class parameter references to be created and uncovered the problem.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a reproducer for the community build failure of h8io/borscht reported in #15647
Compiler version
3.2.0-RC2
Works in 3.1.3
Minimized code
Output
The text was updated successfully, but these errors were encountered: