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++/100667] [11/12/13/14 Regression] std::tuple<A&&> cannot be constructed from A&&, if A not defined (only forward declared)
Date: Wed, 27 Mar 2024 14:14:38 +0000	[thread overview]
Message-ID: <bug-100667-4-P7mPhKBtf7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100667-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Oh interestingly __is_constructible(Incomplete&&, Incomplete) is already
allowed, but __is_nothrow_constructible and __is_convertible give errors:


__is_nothrow_constructible(Incomplete&&, Incomplete)

<stdin>: In function ‘int main()’:
<stdin>:117:68: error: invalid use of incomplete type ‘struct Incomplete’
[-fpermissive]
<stdin>:110:8: note: forward declaration of ‘struct Incomplete’

__is_convertible(Incomplete, Incomplete&&)

<stdin>: In function ‘int main()’:
<stdin>:117:58: error: invalid use of incomplete type ‘struct Incomplete’
[-fpermissive]
<stdin>:110:8: note: forward declaration of ‘struct Incomplete’

  parent reply	other threads:[~2024-03-27 14:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  8:00 [Bug libstdc++/100667] New: " piotrwn1 at gmail dot com
2021-05-19  9:09 ` [Bug libstdc++/100667] [11/12 Regression] " redi at gcc dot gnu.org
2021-06-18  7:56 ` ostash at ostash dot kiev.ua
2021-07-28  7:07 ` rguenth at gcc dot gnu.org
2022-04-21  7:49 ` rguenth at gcc dot gnu.org
2023-05-29 10:05 ` [Bug libstdc++/100667] [11/12/13/14 " jakub at gcc dot gnu.org
2023-05-29 11:16 ` piotrwn1 at gmail dot com
2024-03-27 12:59 ` redi at gcc dot gnu.org
2024-03-27 13:36 ` redi at gcc dot gnu.org
2024-03-27 14:02 ` redi at gcc dot gnu.org
2024-03-27 14:03 ` redi at gcc dot gnu.org
2024-03-27 14:14 ` redi at gcc dot gnu.org [this message]
2024-03-27 17:44 ` redi at gcc dot gnu.org
2024-03-28 18:26 ` cvs-commit at gcc dot gnu.org
2024-03-28 22:33 ` [Bug libstdc++/100667] [11/12/13 " redi at gcc dot gnu.org
2024-05-01 20:31 ` cvs-commit 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-100667-4-P7mPhKBtf7@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).