Correct Unicode for [lg]napprox #26010
Merged
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
timhoffm
approved these changes
May 30, 2023
|
I think that if anything, one can add a note to #25933 stating that some relational operators have been added and corrected? |
Closed
5 tasks
ksunden
approved these changes
Jun 14, 2023
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.
PR summary
While checking the output of #25933 I realized that these two used the wrong code point (prec/succnapprox). (Visible in the current documentation as well.)
See the resulting docs, but to confirm that these are the correct ones: https://www.compart.com/en/unicode/U+2A89 https://www.compart.com/en/unicode/U+2A8A
PR checklist