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++/89855] Inconsistent global namespace overload sets from #include <cmath>
Date: Wed, 29 Apr 2020 20:46:03 +0000	[thread overview]
Message-ID: <bug-89855-4-8MVZoyR5o0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89855-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89855

--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
That's one possible reading, but I don't think the text you quote is precise
enough to say that reading is definitely correct or not. If that is what it
says, it might be unintentional. That paragraph is hardly a paragon of
precision. The current wording was added by https://wg21.link/lwg456 to address
the problem that the original wording didn't reflect reality and was
effectively unimplementable for some vendors. I see nothing in 456 that implies
your reading was intended (and nothing impying it wasn't).

It doesn't really make any difference anyway, since I already plan to change
libstdc++ to resolve the original problem described above.

  parent reply	other threads:[~2020-04-29 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89855-4@http.gcc.gnu.org/bugzilla/>
2020-04-29 18:25 ` foom at fuhm dot net
2020-04-29 18:27 ` foom at fuhm dot net
2020-04-29 20:46 ` redi at gcc dot gnu.org [this message]
2021-11-17 16:05 ` redi at gcc dot gnu.org
2022-02-10  9:41 ` redi at gcc dot gnu.org
2024-03-26 16:51 ` redi at gcc dot gnu.org
2024-03-26 19:37 ` redi at gcc dot gnu.org
2024-03-28  8:12 ` de34 at live dot cn

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-89855-4-8MVZoyR5o0@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).