-
Notifications
You must be signed in to change notification settings - Fork 85
Hashable1 #114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Also, the reason I would like these in
With the current split between |
@tibbe I don't know if you ever had a chance to think about this, but I just ran into a situation where I needed this again, so I thought I would bring it back up. Since I first raised this issue, the Also, just to clarify, the
I will gladly do all of the work needed to make this happen. Let me know if you would accept a PR that implements this. |
Just so I can put this in perspective, can you give an example of how you'd use this? P.S. We need to support the 3 last releases of GHC, so we would still have to rely on transformers if we went ahead with this. |
The simplest demonstration of its utility is the
But it shows up elsewhere. Many data types that are parameterized over a
I'm fine with leaving out the On Tue, Oct 18, 2016 at 01:59:42PM -0700, Johan Tibell wrote:
|
Perhaps we should add it to a new |
I'm fine with exposing through a new module instead of through |
No problem putting the implementation in |
Cool. I'll PR sometime tomorrow. |
It looks like Edward Kmett has already done something like this in the hashable-extras package, but I'd like to propose that the classes
Hashable1
andHashable2
be added tohashable
. To be able to provide a lot of more useful instances of these,hashable
would also need to depend ontransformers
(just for the data types in theData.Functor.*
modules, not for any of the monad transformers). What do you think of this?The text was updated successfully, but these errors were encountered: