Slowly reaching the conclusion that Scala's import statement is a bit broken and that all imports should be fully qualified, all the time.
-
-
-
Replying to @tpolecat
Oh, not much to say. I'm going through some old code and having a nightmare working out what comes from where because of: * the "package" trick (package a.b, package c => implicit import a.b._) * contextual imports (import a, import b - is b b, or a.b?)
2 replies 0 retweets 2 likes -
Replying to @NicolasRinaudo @tpolecat
So I'm basically rewriting everything to fully qualified paths, dropping all `a._` that are not used to import implicits, and flattening my package declarations. More verbose, but sanity restored.
1 reply 0 retweets 0 likes -
Replying to @NicolasRinaudo
I think the generality is good and makes the language more consistent, but yeah it allows you to make a mess of things.
1 reply 0 retweets 2 likes -
Replying to @tpolecat @NicolasRinaudo
My petty complaint is that `_root_` is ugly to look at so I don't use it. Literally that's the only reason. If I could say `import .foo.Bar` (as one would expect as a reasonable person) I would do it all the time.
4 replies 0 retweets 8 likes
The only reason, but there could be no better reason.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.