[darcs-devel] should we import entire modules to avoid conflicts?

Ian Lynagh igloo at earth.li
Mon May 23 16:02:27 PDT 2005


On Sun, May 22, 2005 at 08:05:36AM -0400, David Roundy wrote:
> 
> I've been thinking that perhaps it might be an idea to switch to a policy
> of importing entire modules like
> 
> import FileName
> 
> rather than
> 
> import FileName ( FileName, fn2fp, fp2fn, norm_path )
> 
> I like the latter, since it makes it very easy to see which module a given
> function is from,

I agree; and I think this can make even more difference to people new to
the code.

> On the other hand, a lot of the conflicts we see in darcs-unstable
> are in the modification of import statements, and resolving these conflicts
> is a pain.

A Haskell-specific external merge tool (or a Haskell module for a
generic one) might help here.

> I'm really not decided on this question, so please speak up.

My vote is to keep them.


Thanks
Ian





More information about the darcs-devel mailing list