Re: How to use Data.Set.Set

2005-10-12 Thread Christian Maeder

Ketil Malde wrote:

Indeed.  While I generally like the overloaded, qualified names, I
find it annoying when, like 'map', they clash with Prelude imports.
Which means that, in a module using Data.Set, I must either use it all
qualified, or import it twice (qualified and hiding map), or
explicitly import Prelude hiding map.  (Better solutions wanted!)


I think, you should

 import qualified Data.Set as Set

only and use Set.map rather than the deprecated mapSet

(most other names from Data.Set make more sense with the Set. prefix)

Christian
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: How to use Data.Set.Set

2005-10-12 Thread Ketil Malde
Christian Maeder [EMAIL PROTECTED] writes:

 I think, you should

   import qualified Data.Set as Set

 only and use Set.map rather than the deprecated mapSet

 (most other names from Data.Set make more sense with the Set. prefix)

I can do this of course, but I think it would be nice to be able to
use it unqualified in modules that only uses Sets (and doesn't use
e.g. Maps or List.(null|map)).  If I always have to qualify it, what
is the advantage of Set.map instead of mapSet?

(Oh, right, I can import qualified List as Set -- but then I still
have to change member to elem etc etc.)

-k
-- 
If I haven't seen further, it is by standing in the footprints of giants

___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: How to use Data.Set.Set

2005-10-12 Thread Christian Maeder

Ketil Malde wrote:

the advantage of Set.map instead of mapSet?


Well, you know that the unqualified name is map, i.e. also for 
Data.Map it's not mapMap or mapFM but YourChoice.map.



(Oh, right, I can import qualified List as Set -- but then I still
have to change member to elem etc etc.)


I think, that was discussed when including Data.Set and Data.Map (but 
only isEmpty became null). Replacing the import of Set by List does not 
work well, but Data.Set could be easily replaced by a different Set 
implementation with the same (or a similar enough) interface.


Christian
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users