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++/106376] [LWG3545] The implementation of std::pointer_traits seems wrong
Date: Thu, 21 Jul 2022 09:06:04 +0000 [thread overview]
Message-ID: <bug-106376-4-ThJwfuhoYw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106376-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106376
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |SUSPENDED
Ever confirmed|0 |1
Last reconfirmed| |2022-07-21
Summary|The implementation of |[LWG3545] The
|std::pointer_traits seems |implementation of
|wrong |std::pointer_traits seems
| |wrong
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to 康桓瑋 from comment #0)
> libstdc++ specifies element_type as a meaningless type, so the static_assert
> still passes.
>
> Although the behavior of libstdc++ is incorrect, but I am not feel good
> about this static_assert hard error..
Right, it's completely unusable, see PR 96416.
Libstdc++ already implements my proposed solution, the standard just hasn't
caught up yet ;-)
Suspending until 3545 is resolved, but I expect to close this at some future
date, as there's nothing for libstdc++ to do here.
next prev parent reply other threads:[~2022-07-21 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 3:56 [Bug libstdc++/106376] New: " hewillk at gmail dot com
2022-07-21 4:09 ` [Bug libstdc++/106376] " hewillk at gmail dot com
2022-07-21 9:06 ` redi at gcc dot gnu.org [this message]
2023-04-26 21:47 ` [Bug libstdc++/106376] [LWG3545] " 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-106376-4-ThJwfuhoYw@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).