-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
1:3 != collect(1:3) #13565
Comments
Yes, ranges are not equal to non-ranges because otherwise hashing a range would require hashing every element, which could take quite a while. |
See also #5778 (comment), #6084, #12226 |
Ah, thanks, not sure how I forgot these discussions. Looks like the two most recent comments at #12226 (comment) point to a possible solution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is the fact that
1:3 != collect(1:3)
intended? I can see in the definition of==
that comparisons betweenRange
andArray
are explicitly handled to returnfalse
, but I can't find a good reason for that.The text was updated successfully, but these errors were encountered: