You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I follow the warning recommendation and move a class out of a package object, then recompile without cleaning, I get a generic, tautological error message:
pkgobjection.scala:9:error: NoLongerImplementedError is already defined asclassNoLongerImplementedError
It would be nicer to specify: "...as class NoLongerImplementedError in package object pkgobjection."
I've read and understood #4344, and I've read and misunderstood #4695.
The spec says I should never (for now) let this happen, and maybe it doesn't in a tooled environment.
The text was updated successfully, but these errors were encountered:
@som-snytt said:
Coincidentally, if I had waited awhile and used a compiler with
8068e1208466ab17af40c2670230ba5ac9704e0c,
I would never have known to repackage my little Error class and encounter this situation until one day my compile failed and someone said:
"-Xlint would have told you not to do that".
Medical research has shown that repeated head slaps can cause mini-concussions, dementia and early demise.
If I follow the warning recommendation and move a class out of a package object, then recompile without cleaning, I get a generic, tautological error message:
It would be nicer to specify: "...as class NoLongerImplementedError in package object pkgobjection."
I've read and understood #4344, and I've read and misunderstood #4695.
The spec says I should never (for now) let this happen, and maybe it doesn't in a tooled environment.
The text was updated successfully, but these errors were encountered: