-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Overload resolution vs. a vararg method breaks when a type argument is set explicitly #15913
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
Comments
neko-kai
added a commit
to 7mind/izumi
that referenced
this issue
Aug 25, 2022
neko-kai
added a commit
to 7mind/izumi
that referenced
this issue
Aug 25, 2022
Still reproducible on the current |
It also works to remove the default args. There are a few tickets about unhappy interaction with defaults and overloads. Despair at #12679 (comment) |
ckipp01
added a commit
to ckipp01/dotty
that referenced
this issue
May 24, 2023
[skip community_build] closes scala#15913
nicolasstucki
added a commit
that referenced
this issue
May 25, 2023
Kordyjan
added a commit
that referenced
this issue
Nov 17, 2023
Backports #17576 to the LTS branch. PR submitted by the release tooling.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compiler version
3.1.3 and 3.2.0-RC1
Minimized code
runnable: https://scastie.scala-lang.org/zgzJSXSgQ4uLcczMlsoFOw
Output
Expectation
Expected to compile successfully, as in Scala 2: https://scastie.scala-lang.org/nvb0KV3cTHeJloTyW1SY8g
Workaround: removing the explicit type argument fixes the error:
The text was updated successfully, but these errors were encountered: