public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104242] [12 Regression] Class with constructor from std::any is not copyable
Date: Fri, 23 Jun 2023 12:56:52 +0000	[thread overview]
Message-ID: <bug-104242-4-Q78TkFWtqi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104242-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:5fc6b3a03355e1f77a7c38c0fa7afb0822ad954f

commit r11-10870-g5fc6b3a03355e1f77a7c38c0fa7afb0822ad954f
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Mar 18 13:10:01 2022 +0000

    libstdc++: Simplify constraints for std::any construction [PR104242]

    Partially revert r12-4190-g6da36b7d0e43b6f9281c65c19a025d4888a25b2d
    because using __and_<..., is_copy_constructible<T>> when T is incomplete
    results in an error about deriving from is_copy_constructible<T> when
    that is incomplete. I don't know how to fix that, so this simply
    restores the previous constraint which worked in this case (even though
    I think it's technically undefined to use is_copy_constructible<T> with
    incomplete T). This doesn't restore exactly what we had before, but uses
    the is_copy_constructible_v and __is_in_place_type_v variable templates
    instead of the ::value member.

    libstdc++-v3/ChangeLog:

            PR libstdc++/104242
            * include/std/any (any(T&&)): Revert change to constraints.
            * testsuite/20_util/any/cons/104242.cc: New test.

    (cherry picked from commit 7a42b1fa1a090ead96cc0f94a8060a9650c810d5)

      parent reply	other threads:[~2023-06-23 12:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 12:51 [Bug c++/104242] New: " fchelnokov at gmail dot com
2022-01-26 12:52 ` [Bug c++/104242] " fchelnokov at gmail dot com
2022-01-26 13:06 ` [Bug c++/104242] [12 Regression] " rguenth at gcc dot gnu.org
2022-01-26 19:03 ` [Bug libstdc++/104242] " pinskia at gcc dot gnu.org
2022-01-26 19:05 ` pinskia at gcc dot gnu.org
2022-03-09 13:21 ` rguenth at gcc dot gnu.org
2022-03-18 15:42 ` cvs-commit at gcc dot gnu.org
2022-03-18 17:48 ` redi at gcc dot gnu.org
2023-06-23 12:56 ` cvs-commit at gcc dot gnu.org [this message]

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-104242-4-Q78TkFWtqi@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).