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++/100900] error: missing 'typename' prior to dependent type name in <ranges> elements_view
Date: Mon, 07 Jun 2021 15:20:27 +0000 [thread overview]
Message-ID: <bug-100900-4-ZA9Pg3RtDa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100900-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100900
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:
https://gcc.gnu.org/g:5e2e15f212e2458a1258b8c856895c755460bc6b
commit r12-1262-g5e2e15f212e2458a1258b8c856895c755460bc6b
Author: Avi Kivity <avi@scylladb.com>
Date: Mon Jun 7 11:19:05 2021 -0400
libstdc++: add missing typename for dependent type in ranges::elements_view
[PR100900]
Clang complains about the missing typename. I believe it's not required
in a more complete implementation of C++, but it's nicer to support
less complete implementations.
PR libstdc++/100900
libstdc++-v3/ChangeLog:
* include/std/ranges (elements_view::__iter_cat::_S_iter_cat):
Add missing typename.
next prev parent reply other threads:[~2021-06-07 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 6:54 [Bug libstdc++/100900] New: " avi@cloudius-systems.com
2021-06-04 7:48 ` [Bug libstdc++/100900] " hewillk at gmail dot com
2021-06-04 9:25 ` redi at gcc dot gnu.org
2021-06-07 13:14 ` ppalka at gcc dot gnu.org
2021-06-07 13:28 ` avi@cloudius-systems.com
2021-06-07 13:35 ` ppalka at gcc dot gnu.org
2021-06-07 15:20 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-07 15:24 ` cvs-commit at gcc dot gnu.org
2021-06-07 15:30 ` ppalka at gcc dot gnu.org
2021-06-07 15:49 ` avi@cloudius-systems.com
2021-07-05 0:57 ` ldv at sourceware dot org
2021-07-06 19:36 ` cvs-commit at gcc dot gnu.org
2021-07-06 19:46 ` ppalka 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-100900-4-ZA9Pg3RtDa@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).