public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Patrick Palka <ppalka@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r11-8519] libstdc++: add missing typename for dependent type in ranges::elements_view [PR100900]
Date: Mon,  7 Jun 2021 15:24:27 +0000 (GMT)	[thread overview]
Message-ID: <20210607152427.0E4D03892453@sourceware.org> (raw)

https://gcc.gnu.org/g:23fa1e7eab7680ae0488b4c8802b0bcd8f78425d

commit r11-8519-g23fa1e7eab7680ae0488b4c8802b0bcd8f78425d
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.
    
    (cherry picked from commit 5e2e15f212e2458a1258b8c856895c755460bc6b)

Diff:
---
 libstdc++-v3/include/std/ranges | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/include/std/ranges b/libstdc++-v3/include/std/ranges
index ae3cd7fbc99..0dd4fb6a9a5 100644
--- a/libstdc++-v3/include/std/ranges
+++ b/libstdc++-v3/include/std/ranges
@@ -3463,7 +3463,7 @@ namespace views::__adaptor
 	  static auto _S_iter_cat()
 	  {
 	    using _Base = elements_view::_Base<_Const>;
-	    using _Cat = iterator_traits<iterator_t<_Base>>::iterator_category;
+	    using _Cat = typename iterator_traits<iterator_t<_Base>>::iterator_category;
 	    using _Res = decltype((std::get<_Nm>(*std::declval<iterator_t<_Base>>())));
 	    if constexpr (!is_lvalue_reference_v<_Res>)
 	      return input_iterator_tag{};


                 reply	other threads:[~2021-06-07 15:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210607152427.0E4D03892453@sourceware.org \
    --to=ppalka@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).