Overloaded names for Map/Set?
iavor.diatchki at gmail.com
Fri May 24 15:16:53 UTC 2019
I think refactoring to use consistent naming is a good idea, but I am not
sure about the class idea.
To see if it is viable, we should list the types in question and the
operations we'd like to overload.
I find that with containers there tend to be two cases: either the
operations are similar but not exactly the same and you have to do type
hackery to make things fit, or you realize that you can just use the same
type in multiple places.
On Fri, May 24, 2019, 07:12 Andreas Klebinger <klebinger.andreas at gmx.at>
> Hello devs,
> I would appreciate feedback on the idea in
> 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!
> ghc-devs mailing list
> ghc-devs at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs