Skip to content
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.

Sign up for GitHub

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

Jump to bottom

It is bad to check equivalence, when all you need to know is identicalness #13

Open
mulkieran opened this issue Mar 7, 2016 · 1 comment
Open

It is bad to check equivalence, when all you need to know is identicalness #13

mulkieran opened this issue Mar 7, 2016 · 1 comment

Comments

@mulkieran
Copy link
Owner

Because equivalence is so much more expensive.
@mulkieran
Copy link
Owner Author

It may be, that if something is equivalent you find it rapidly, but if not it may take a while to get a negative result. But, in this instance, a disk had actually changed its location, so it is not clear to me why failure wasn't rapid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mulkieran