[Haskell-cafe] possible bug in default module lookup scheme / or invalid haskell?

Kevin Quick quick at sparq.org
Mon Jul 19 10:51:30 EDT 2010

On Sun, 18 Jul 2010 12:02:39 -0700, Carter Schonwald <carter.schonwald at gmail.com> wrote:

> nope, I was suggesting rather:
> ./A.hs has module A which has an import A.B line
> ./A/ has  B.hs with module A.B  which imports A.B.C
>  /C which has module A.B.C in file C.hs
> I think this scenario  should work ....
> -carter

It's an interesting proposal, but unfortunately there's the possibility of an n:1 mapping between parent directory and child.  This would make using ".." against the current working directory potentially non-deterministic, and removing lower elements from an absolute path wouldn't necessarily get you back to the directory where A.hs lived either.


More information about the Haskell-Cafe mailing list