-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Compiler crashes on overloaded methods with varargs of generic types on JS classes #18658
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
Labels
Comments
sjrd
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 6, 2023
When extracting the type of a varargs parameter, we have to go back to before erasure. However, that gives us a non-erased type inside as well. We need to re-erase that type to get something sensible for the back-end.
sjrd
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 6, 2023
When extracting the type of a varargs parameter, we have to go back to before erasure. However, that gives us a non-erased type inside as well. We need to re-erase that type to get something sensible for the back-end.
sjrd
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 6, 2023
When extracting the type of a varargs parameter, we have to go back to before erasure. However, that gives us a non-erased type inside as well. We need to re-erase that type to get something sensible for the back-end.
Thanks for the report. PR at #18659. |
sjrd
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 11, 2023
When extracting the type of a varargs parameter, we have to go back to before erasure. However, that gives us a non-erased type inside as well. We need to re-erase that type to get something sensible for the back-end.
sjrd
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 12, 2023
When extracting the type of a varargs parameter, we have to go back to before erasure. However, that gives us a non-erased type inside as well. We need to re-erase that type to get something sensible for the back-end.
nicolasstucki
added a commit
that referenced
this issue
Oct 16, 2023
When extracting the type of a varargs parameter, we have to go back to before erasure. However, that gives us a non-erased type inside as well. We need to re-erase that type to get something sensible for the back-end.
nicolasstucki
pushed a commit
to dotty-staging/dotty
that referenced
this issue
Oct 19, 2023
When extracting the type of a varargs parameter, we have to go back to before erasure. However, that gives us a non-erased type inside as well. We need to re-erase that type to get something sensible for the back-end.
WojciechMazur
pushed a commit
that referenced
this issue
Jun 21, 2024
When extracting the type of a varargs parameter, we have to go back to before erasure. However, that gives us a non-erased type inside as well. We need to re-erase that type to get something sensible for the back-end. [Cherry-picked 4538875]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compiler version
Scala 3.3.1, Scala.js 1.14.0
Minimized code
There's something about varargs with
Tuple2
orProduct2
that it does not like. Not every type causes this crash.Output
Scala 3.3.1 compiler crashes (Scala 2.13.9 does not). Output below.
Note: I censored some paths with
<projectpath>
and<userhome>
.Expectation
The compiler shouldn't crash.
The text was updated successfully, but these errors were encountered: