public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/113060] std::variant converting constructor/assignment is non-conforming after P2280?
Date: Mon, 19 Feb 2024 09:11:14 +0000 [thread overview]
Message-ID: <bug-113060-4-iVEPwrDRJM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113060-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113060
--- Comment #6 from Jiang An <de34 at live dot cn> ---
(In reply to Jiang An from comment #5)
> `decltype(std::declval<auto (*)(_Tp&& __t) ->
> decltype(_Arr<_Ti>{{std::forward<_Tp>(__t)}})>(std::declval<_Tp>()))`
Typo, this should be
`decltype(std::declval<auto (*)(_Tp&& __t) ->
decltype(_Arr<_Ti>{{std::forward<_Tp>(__t)}})>()(std::declval<_Tp>()))`.
next prev parent reply other threads:[~2024-02-19 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 9:32 [Bug libstdc++/113060] New: " dangelog at gmail dot com
2023-12-18 11:18 ` [Bug libstdc++/113060] " redi at gcc dot gnu.org
2023-12-18 14:32 ` dangelog at gmail dot com
2024-02-16 14:43 ` redi at gcc dot gnu.org
2024-02-19 8:07 ` de34 at live dot cn
2024-02-19 9:07 ` de34 at live dot cn
2024-02-19 9:11 ` de34 at live dot cn [this message]
2024-02-19 23:47 ` dangelog at gmail dot com
2024-02-20 1:47 ` de34 at live dot cn
2024-02-20 10:09 ` dangelog at gmail dot com
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-113060-4-iVEPwrDRJM@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).