public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "avi@cloudius-systems.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/100900] New: error: missing 'typename' prior to dependent type name in <ranges> elements_view Date: Fri, 04 Jun 2021 06:54:38 +0000 [thread overview] Message-ID: <bug-100900-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100900 Bug ID: 100900 Summary: error: missing 'typename' prior to dependent type name in <ranges> elements_view Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: avi@cloudius-systems.com Target Milestone: --- clang++ complains: /usr/lib/gcc/x86_64-redhat-linux/11/../../../../include/c++/11/ranges:3392:19: error: missing 'typename' prior to dependent type name 'iterator_traits<iterator_t<_Base>>::iterator_category' using _Cat = iterator_traits<iterator_t<_Base>>::iterator_category;
next reply other threads:[~2021-06-04 6:54 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-04 6:54 avi@cloudius-systems.com [this message] 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 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@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: linkBe 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).