FWIW, a while ago I talked to one of the guys working on the official
Eclipse Scala plugin. He said that Scala's policy of allowing imports
pretty much everywhere made it quite hard to build an IDE that's
responsive on large codebases. It's not quite the same, because Scala
allows much more than just imports at the bottom, but still...
Regards
Dominique
2014-04-22 19:59 GMT+02:00 Thiago Negri
When reading code, I find it quite distracting to have to get past the import list to reach the actual module code, as the import list can be (and often is) quite big.
So, why not issue import statements at the bottom of a module file?
Likewise, we can use "where" statements to define names used in a function after using them, so they don't distract the reader.
I'm against imports at the middle of the file. But I guess being able to issue them at the end of the module could make sense if you want to get the reader straight to the code.
A language pragma could be used to select between top imports or bottom imports (can't use both).
What do you think?
Example:
""" {-# LANGUAGE LateImports #-} module Foo where
bar :: String bar = "quux"
baz :: Fiz baz = mkFiz
import Fiz (Fiz, mkFiz) """
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe