-
Notifications
You must be signed in to change notification settings - Fork 702
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
Order.reverseOrder Should tie the knot #870
Comments
Hmm, is there perhaps a better way to pass around the original |
@markfarrell I'm alternating between Order and Order.reverseOrder. |
seems like it wouldn't be hard to override reverseOrder in the anonymous instance created by reverseOrder to return self |
Issue #870: Made Order.reverseOrder tie the knot.
Order.reverseOrder.reverseOrder should result in the original order instance.
(It actually is one of the performance bottlenecks in my application right now)
It may also override the other methods in Order - as lessThan, greaterThan and the others,
As computing the ordering is usually more expensive than calling the appropriate comparison function directly.
The text was updated successfully, but these errors were encountered: