On 25/04/2014 21:26, Malcolm Wallace wrote:
On 25 Apr 2014, at 14:17, Simon Marlow wrote:
The problem we often have is that when you're writing code for a library that
lives deep in the module hierarchy, you end up needing a deep directory
structure, where the top few layers are all empty.
I don't see how this is a problem at all. Navigating the "vacuous" structure
is as simple as pressing the tab key a few times. But if you change the mapping
convention between files and module names, you need to do it for all tools, not just the
compiler. I imagine all of the following tools would need to know about it:
cabal, hoogle, haddock, happy, alex, hat, hsc2hs
So actually many of these tools don't need to map module names to source
files, so they work unchanged. Only Cabal definitely needs changes, I'm
not sure about hoogle and hat but I suspect they would be fine.
and probably a few more. The feature seems like a very low power-to-weight
ratio, so -1 from me.
Fair enough :)
Cheers,
Simon
Regards,
Malcolm
_______________________________________________
Glasgow-haskell-users mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
_______________________________________________
Glasgow-haskell-users mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users