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 .map.
(Oh, right, I can "import qualified List as Set" -- but then I still
have to change "member" to "elem" etc etc.)
I th
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 t
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
