public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/110719] Should chrono formatters always use std::time_put for locale's representation? Date: Wed, 19 Jul 2023 11:39:20 +0000 [thread overview] Message-ID: <bug-110719-4-4duwMPk6v0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110719-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110719 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #0) > Should we consistently use std::time_put for all locale-specific output? > Alternatively, we could use time_point_cast and duration_cast to round to > seconds. None of the locale-specific formats print fractional seconds. This has now been implemented on trunk. > It would be useful to profile std::format with and without std::time_get, to > see if reusing std::format performs better. If it doesn't, using > std::time_put might be simpler. This profiling would still be useful.
next prev parent reply other threads:[~2023-07-19 11:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-18 14:43 [Bug libstdc++/110719] New: " redi at gcc dot gnu.org 2023-07-19 10:13 ` [Bug libstdc++/110719] " redi at gcc dot gnu.org 2023-07-19 10:37 ` redi at gcc dot gnu.org 2023-07-19 11:37 ` cvs-commit at gcc dot gnu.org 2023-07-19 11:39 ` redi at gcc dot gnu.org [this message] 2023-07-19 15:51 ` cvs-commit at gcc dot gnu.org 2023-07-28 17:32 ` cvs-commit at gcc dot gnu.org 2023-07-28 17:32 ` cvs-commit at gcc dot gnu.org 2023-07-28 18:59 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-110719-4-4duwMPk6v0@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).