-
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
Member selection does not take GADT constraints into account #7044
Labels
Comments
Hi thanks for reporting, this is very related to #6323, perhaps you could add your comments to it? |
Yeah this is a duplicate of #6323 |
Opening in preference to #6323. |
abgruszecki
changed the title
GADTs inference is very weak in Dotty
Member selection does not take GADT constraints into account
Aug 15, 2019
radeusgd
referenced
this issue
in radeusgd/dotty
Apr 15, 2020
radeusgd
referenced
this issue
in radeusgd/dotty
Apr 15, 2020
radeusgd
referenced
this issue
in radeusgd/dotty
Apr 22, 2020
radeusgd
referenced
this issue
in radeusgd/dotty
Apr 22, 2020
radeusgd
referenced
this issue
in radeusgd/dotty
Apr 30, 2020
radeusgd
referenced
this issue
in radeusgd/dotty
May 12, 2020
abgruszecki
added a commit
that referenced
this issue
May 12, 2020
Fix #7044: Approximate GADT bounds to avoid explicit type ascriptions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
minimized code
expectation
As a long-time Haskeller, I would expect the above code to compile without providing the explicit signatures
(body: Int)
and(body: Option[Int])
. The compiler has enough information to know that (especially as it does not allow me to write any other signature there). Writing them by hand is cumbersome and breaks the beauty of GADTs. I feel this is a very serious GADTs limitation in Dotty. I know that in Scala 2.x it was worse and unsound, but what we see in Dotty is rather a partial solution, not a final one.The text was updated successfully, but these errors were encountered: