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

<chrono>: [time.format] may assume that strings are encoded in the active code page #1908

Open
mnatsuhara opened this issue May 4, 2021 · 1 comment
Open

<chrono>: [time.format] may assume that strings are encoded in the active code page #1908

mnatsuhara opened this issue May 4, 2021 · 1 comment
Labels
chrono C++20 chrono

Comments

@mnatsuhara
Copy link
Contributor

We should investigate whether similar changes to #1834 are necessary for <chrono>'s integration with std::format.
@mnatsuhara mnatsuhara added the chrono C++20 chrono label May 4, 2021
@cpplearner
Copy link
Contributor

cpplearner commented Oct 21, 2023 •
edited
Loading

A chrono conversion specifier must start with % (byte 0x25), and % isn't used as a non-lead-byte in any supported multibyte encoding (unlike { and }). So I think no changes are needed.

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

No branches or pull requests
2 participants
@cpplearner @mnatsuhara