public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107085] __reference_constructs_from_temporary does not detect static up-cast
Date: Tue, 04 Oct 2022 19:34:26 +0000 [thread overview]
Message-ID: <bug-107085-4-WPa6OGI9vH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107085-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107085
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Roy Jacobson from comment #3)
> Thanks! But a Base const& is still not detected:
>
> static_assert(__reference_constructs_from_temporary(Base const&, Derived));
>
> And in this case I think it _is_ a bug that this doesn't compile?
To make sure I understand this correctly, __reference_constructs_from_temporary
should say "yes" here, because it's just like
const Base& b(Derived{});
where we bind 'b' to the Base subobject of a temporary Derived object, yes?
next prev parent reply other threads:[~2022-10-04 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 10:30 [Bug c++/107085] New: " roi.jacobson1 at gmail dot com
2022-09-29 10:42 ` [Bug c++/107085] " redi at gcc dot gnu.org
2022-09-29 10:46 ` redi at gcc dot gnu.org
2022-09-29 11:11 ` roi.jacobson1 at gmail dot com
2022-09-29 11:52 ` redi at gcc dot gnu.org
2022-09-29 12:45 ` mpolacek at gcc dot gnu.org
2022-10-04 19:34 ` mpolacek at gcc dot gnu.org [this message]
2022-10-04 20:41 ` mpolacek at gcc dot gnu.org
2022-10-05 6:43 ` redi at gcc dot gnu.org
2022-10-05 15:29 ` mpolacek at gcc dot gnu.org
2022-10-05 16:07 ` mpolacek at gcc dot gnu.org
2022-10-07 22:06 ` cvs-commit at gcc dot gnu.org
2022-10-07 22:06 ` mpolacek 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-107085-4-WPa6OGI9vH@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).