Overloaded names for Map/Set?

Brandon Allbery allbery.b at gmail.com
Fri May 24 14:29:32 UTC 2019

For what it's worth, the Edison packages provide such interfaces for many
structures. You might want to ask about experiences.

On Fri, May 24, 2019, 10:12 Andreas Klebinger <klebinger.andreas at gmx.at>

> Hello devs,
> I would appreciate feedback on the idea in
> https://gitlab.haskell.org/ghc/ghc/merge_requests/934
> Maps/Sets in GHC for the most part offer the same basic functionality
> but their interfaces differ.
> In order to make this easier to work with I propose using overloading
> via IsSet/IsMap classes.
> The goal is to make working with these data structures simpler by having
> a uniform interface
> when it comes to names and argument orders.
> There are downsides, but to me they seem minor. Error messages can be
> more confusing when one
> get's the types wrong. We have to import the class to use it and the like.
> However overall I think making code easier by not having to remember the
> naming scheme + argument order
> for the different possible instances would make this worthwhile.
> But GHC isn't my project but one of the community so please voice your
> opinion on the matter on the
> merge request!
> Cheers
> Andreas
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20190524/b8f8c17c/attachment.html>

More information about the ghc-devs mailing list