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++/104465] std::vector<std::string> should satisfy std::ranges::viewable_range (P2415 for -c++2b)
Date: Wed, 09 Feb 2022 13:35:44 +0000 [thread overview]
Message-ID: <bug-104465-4-z4gYpMBBER@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104465-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104465
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Younan Zhang from comment #0)
> Clang 13 rejects the above code (https://gcc.godbolt.org/z/xoKesEz7q), which
> is as expected.
That's just because Clang is broken and doesn't work with any libstdc++ views:
https://github.com/llvm/llvm-project/issues/44178
So there are several things going on here. You're correct that P2415 is not
implemented, but I think your example is supposed to compile even before that
change. An lvalue vector has always been a viewable range. Clang 13 rejects
your example because it's broken, not because of the viewable_range
requirement.
next prev parent reply other threads:[~2022-02-09 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 12:40 [Bug libstdc++/104465] New: " zyn7109 at gmail dot com
2022-02-09 12:43 ` [Bug libstdc++/104465] " zyn7109 at gmail dot com
2022-02-09 13:16 ` redi at gcc dot gnu.org
2022-02-09 13:22 ` redi at gcc dot gnu.org
2022-02-09 13:24 ` redi at gcc dot gnu.org
2022-02-09 13:35 ` redi at gcc dot gnu.org [this message]
2022-02-09 14:55 ` zyn7109 at gmail dot com
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-104465-4-z4gYpMBBER@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).