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++/112832] [std::format] Broken non-SFINAE-friendly `set_debug_format()` for `const char *` formatter
Date: Mon, 04 Dec 2023 11:36:25 +0000 [thread overview]
Message-ID: <bug-112832-4-ZSHrAaYbQ7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112832-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112832
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-12-04
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
Target Milestone|--- |13.3
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Egor from comment #0)
> GCC doesn't seem to implement `{:?}` debug format for strings yet.
Correct, see PR 109162
> Yet for some reason `std::formatter<const char *>` has a
> `set_debug_format()` function, which causes a hard error when used (isn't
> SFINAE-friendly).
The error has nothing to do with it being SFINAE-friendly or not.
> `set_debug_format()` should be SFINAE-friendly, to allow the user to call it
> conditionally when available.
No, it should just not exist yet.
next prev parent reply other threads:[~2023-12-04 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 16:53 [Bug libstdc++/112832] New: " iamsupermouse at mail dot ru
2023-12-04 11:36 ` redi at gcc dot gnu.org [this message]
2023-12-05 16:49 ` [Bug libstdc++/112832] " cvs-commit at gcc dot gnu.org
2023-12-06 14:44 ` cvs-commit at gcc dot gnu.org
2023-12-06 14:45 ` 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-112832-4-ZSHrAaYbQ7@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: link
Be 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).