-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Ambigious types errors by picking nested/derived type and type defined in the same package #17433
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
I think it's due to #17033. Maybe revert that and check again? |
Seems to be a bug, the ambiguity should only show if |
Probably best to revert it, I'll take a look to submit a fixed version. |
@lrytz maybe just a tweak
I tried it with sangria. Yes, it "pairs well" with sangria! |
Thank you @som-snytt, that looks good to me. I'll PR it tomorrow if you didn't already. |
I'll grant you the honors, like King Charles III, or I guess in Scala it's King Charless. Oh, the pun is also
|
looks obscure to this reader. The intuition may have been that the type parameter is disambiguating. Perhaps it's a good time to try out the new meme: “Borges thinks you should try a little harder.”
|
…rror" This reverts commit 7d4e103. Closes scala#17433
…rror" This reverts commit 7d4e103. Closes scala#17433
Compiler version
3.3.1-RC1-bin-20230504-0e00420-NIGHTLY
Found in Community Build in following projects:
Output
In this case Value is also defined as
sealed trait Value
in other fileExpectation
Should compile
The text was updated successfully, but these errors were encountered: