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 c++/109340] Inconsistent diagnostics for invalid member types in union
Date: Wed, 29 Mar 2023 23:38:37 +0000	[thread overview]
Message-ID: <bug-109340-4-bZLVHRbBtC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109340-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:31a909712014b75fc6ae2ca5eaa425f218bb5f32

commit r13-6934-g31a909712014b75fc6ae2ca5eaa425f218bb5f32
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Mar 29 22:16:55 2023 +0100

    libstdc++: Use std::remove_cv_t in std::optional::transform [PR109340]

    We need to strip cv-qualifiers from the result of the callable passed to
    std::optional::transform.

    For std::expected::transform and std::expected::transform_error I
    noticed we were stripping cv-qualifiers but were also incorrectly
    stripping references.

    libstdc++-v3/ChangeLog:

            PR libstdc++/109340
            * include/std/expected (expected::transform): Use
            std::remove_cv_t instead of std::remove_cvref_t.
            (expected::transform_error): Likewise.
            (expected<cv void, E>::transform): Likewise.
            (expected<cv void, E>::transform_error): Likewise.
            * include/std/optional (transform): Use std::remove_cv_t.
            * testsuite/20_util/optional/monadic/pr109340.cc: New test.

  reply	other threads:[~2023-03-29 23:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 20:55 [Bug c++/109340] New: " redi at gcc dot gnu.org
2023-03-29 23:38 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-29 23:41 ` [Bug c++/109340] " 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-109340-4-bZLVHRbBtC@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).