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++/113154] [11 only] std::views::values not working with rvalue references to ranges
Date: Thu, 28 Dec 2023 01:10:59 +0000 [thread overview]
Message-ID: <bug-113154-4-WubJfIZhNx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113154-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113154
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> I doubt, the patch which fixed this can/will be backported to the GCC 11
> releases.
Right. GCC 11 is correct according to the C++20 standard, but the semantics
were changed after the C++20 standard was published. That was implemented in
GCC with:
commit 5e1b17f038671df1a6580ece4cd58ef91cc1e234
Author: Patrick Palka
Date: Tue Feb 22 09:37:58 2022 -0500
libstdc++: Implement P2415R2 changes to viewable_range / views::all
This implements the wording changes in P2415R2 "What is a view?", which
is a DR for C++20.
I don't think we want to backport it.
prev parent reply other threads:[~2023-12-28 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 2:35 [Bug c++/113154] New: " ivan.lazaric.gcc at gmail dot com
2023-12-27 2:57 ` [Bug libstdc++/113154] [11 only] " pinskia at gcc dot gnu.org
2023-12-28 1:10 ` redi 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-113154-4-WubJfIZhNx@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).