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
Misleading compiler error on wrong import #5389
Comments
Imported From: https://issues.scala-lang.org/browse/SI-5389?orig=1 |
I would have used I thought I understood There is no way of knowing if this is an improvement in terms of user experience, but I see there is no
We must do better for what we call, at least in Montreal, "le pou", the plain old user. These are the users you pick up without noticing until they give you an itch to scratch. |
the Scala 2 error message seems pretty good to me, actually. I don't see value in keeping this ticket open another 7 years. |
NEScala's in NYC next year, so apparently it's the compass point. York is in England, as every Brit knows, but that didn't survive the trip, as any Bostonian knows. As for the error message, it seems like the real problem is that you need a stable path to import from, so Dotty's is more correct. I was on the fence about upgrading but now I'm sold. |
The feature improvement would be to turn off root import of universal members from modules. In scala 3, top level
In scala 2, you witness it only in imports. |
Som Snytt is the Lorax, he speaks for bug #5389 |
Assuming there is no
ne
package, the following top-level import:makes the compiler complain that:
I believe this is misleading for the Plain Old User.
The text was updated successfully, but these errors were encountered: