make ranges and arrays unequal, faster hashing of ranges, fixes #5778 #6084
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix == and isequal of ranges to only compare by components when it is safe to do so (ranges with different types but == components can generate different elements) add float32(x) etc. for FloatRange don't show floating point Range objects using colons, since those construct FloatRanges
JeffBezanson
added a commit
that referenced
this pull request
Mar 11, 2014
make ranges and arrays unequal, faster hashing of ranges, fixes #5778
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix == and isequal of ranges to only compare by components when it is safe to do so
(ranges with different types but == components can generate different elements)
add float32(x) etc. for FloatRange
don't show floating point Range objects using colons, since those construct FloatRanges