-
Notifications
You must be signed in to change notification settings - Fork 89
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
Add Bounded Char instance #37
Conversation
I implemented the values through the FFI to avoid having to move |
Sorry, Just woke up, didn't mean to merge this. Brain is on auto-pilot. I've reverted it for now. PR looks good though. |
Hah, no problem. Merging is fine anyway, the question is just about whether we want to bump to v0.2.0 for this... might be a bit painful as I've still not got a working auto-version-bump tool. |
I think we have to ... right? If someone already has Prelude and installs the latest |
Removing the |
If the previous |
And one final point - the old |
Ah ok. Maybe we can get away with it then? I don't think any code uses this instance yet. But then, we've been bitten by things like this before :( |
Sorry, now I see. Yes, minor version bump for Prelude, major for |
I'll revert my revert then? |
Haha, sure :) |
Alright done, I'll tag. |
So we need to bump everything which depends on |
It's not too bad, I've already started doing it:
|
(enums needed the prelude update first) |
This was previously an orphan in Data.Char, and also was wrong - the bottom and top values were reversed.
I'm not sure whether this is strictly speaking a breaking change or not, so not sure what we want to do about versioning here.