-
Notifications
You must be signed in to change notification settings - Fork 182
Improve Ord IntSet instance #787
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
I'm on it. First step is to trigger the bug in testing. I made an Arbitrary instance that produces larger numbers jwaldmann@80af818 (this may be generally useful?) and then indeed I am seeing the mis-behaviour with
I will next look into a proposed fix jwaldmann@259b737 but it's not working as-is. |
This
this is probably related to some overflow that changes the sign. Yes - 182b06b looks good now. |
How should I proceed here? I think the issue is fixed. Rebase the fix on #788? |
Weren't you trying to fix the clever instance? |
I think I did ( containers/containers/src/Data/IntSet/Internal.hs Line 1217 in 182b06b
|
I feel like there's some communication issue going on here, but I'm confused as to who doesn't understand whom and why. Yes, I'd expect you to rebase your improvement branch on master and submit a PR, but if you have other intentions just explain again please. |
Sorry for being not clear. I was waiting for #788 to land. It is orthogonal in the source - the connection is that it would have caught the bug in this "clever" instance. Anyway I will base on (current) master. |
@jwaldmann any chance you would want to try this again, since #788 is resolved? |
yes I will look into this. |
@jwaldmann just checking if you made some progress on this. Would be nice to wrap this up. I could give it a try if you've been too busy. |
Sorry for the ongoing delay, and thanks for the offer. I am trying this week. After that - you may take over. |
@jwaldmann, any luck? |
I'll try implementing this tomorrow. |
An attempt was made in #670, but it proved to have some subtle bug in #783 and had to be reverted. It would be nice to fix and reinstate.
The text was updated successfully, but these errors were encountered: