-
Notifications
You must be signed in to change notification settings - Fork 1.7k
<format> Properly handle multibyte encodings in format strings #1815
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
Merged
Casey Carter (CaseyCarter)
merged 10 commits into
microsoft:feature/format
from
CaseyCarter:gh1576
Apr 9, 2021
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
36cbbe7
Properly handle multibyte encodings in format strings
CaseyCarter 433acae
Merge remote-tracking branch 'origin/feature/format' into gh1576
CaseyCarter 2957cb9
Casey's review comments
CaseyCarter fc38447
one more comment cleanup
CaseyCarter 2e05f65
Remove constexpr from P0355R7_calendars_and_time_zones_formatting.
StephanTLavavej 2eec644
Workaround VSO-1308657 "Standard Library Header Units: std::projected…
StephanTLavavej 04d4497
Use int instead of ptrdiff_t for width estimation
CaseyCarter e52dde5
Sundry review comments
CaseyCarter da5378d
test update
CaseyCarter 92e0bca
MOAR comments
CaseyCarter File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not get why we are pulling those algorithms out. We do not really want the bounds checks and we already have the unchecked iterators ready.
Why not simply call
_RANGES _Find_uncheckedand_RANGES _Copy_unchecked?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For calling directly with range arguments when we don't have iterators handy, it's much simpler to call the range algorithm. (Recall that Range algorithms with range arguments don't perform bounds checks - they trust that
begin()andend()return a valid range.)