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++/101258] std ::is_integral_v is undocumented Date: Wed, 30 Jun 2021 20:17:16 +0000 [thread overview] Message-ID: <bug-101258-4-4Ya0uIfVvk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101258-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101258 --- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> --- Lots of things in our API docs are not in the standard, and lots of things in the standard are not in our API docs. If you're trying to use it for that, no wonder it's painful. Stop it.
next prev parent reply other threads:[~2021-06-30 20:17 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-29 14:25 [Bug libstdc++/101258] New: " giecrilj at stegny dot 2a.pl 2021-06-29 16:08 ` [Bug libstdc++/101258] " redi at gcc dot gnu.org 2021-06-29 16:13 ` redi at gcc dot gnu.org 2021-06-29 21:16 ` giecrilj at stegny dot 2a.pl 2021-06-29 21:18 ` giecrilj at stegny dot 2a.pl 2021-06-30 10:05 ` redi at gcc dot gnu.org 2021-06-30 10:28 ` redi at gcc dot gnu.org 2021-06-30 12:10 ` giecrilj at stegny dot 2a.pl 2021-06-30 12:27 ` giecrilj at stegny dot 2a.pl 2021-06-30 20:16 ` redi at gcc dot gnu.org 2021-06-30 20:17 ` redi at gcc dot gnu.org [this message] 2021-06-30 20:26 ` pinskia at gcc dot gnu.org 2021-06-30 20:39 ` giecrilj at stegny dot 2a.pl 2021-06-30 20:41 ` redi at gcc dot gnu.org 2021-06-30 20:44 ` giecrilj at stegny dot 2a.pl 2021-06-30 23:02 ` redi at gcc dot gnu.org 2021-07-01 0:08 ` cvs-commit at gcc dot gnu.org 2021-07-01 0:12 ` redi at gcc dot gnu.org 2021-07-01 8:04 ` redi at gcc dot gnu.org 2021-08-11 15:42 ` cvs-commit at gcc dot gnu.org 2021-08-11 15:43 ` 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-101258-4-4Ya0uIfVvk@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).