Fix vec_proxy_compare() example #1977
Open
Conversation
This file contains hidden or 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
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.
When introducing custom implementation of
vec_proxy_compare(), the examplerational(2, 4) < rational(2, 3)was used as a case where we would get aFALSEresult. This actually renderedTRUE, because of fallback tovec_proxy_equal(), which uses the irreducible fraction, so it was actually equivalent torational(1, 2) < rational(2, 3), which isTRUEeven lexicographically. This example was thus misleading, and I changed it torational(2, 5) < rational(2, 3), which correctly showcases the problem.I also added an additional paragraph warning about floating point precision when using the double representation as a proxy.