public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-8015] libstdc++: Remove redundant partial specialization in _Nth_type
Date: Wed,  8 Nov 2023 13:18:40 +0000 (GMT)	[thread overview]
Message-ID: <20231108131840.7480E3858C5E@sourceware.org> (raw)

https://gcc.gnu.org/g:c6e03a1c54451eaab872dcdd8ab927b7efe16c9c

commit r13-8015-gc6e03a1c54451eaab872dcdd8ab927b7efe16c9c
Author: Feng Jisen <J1senn@outlook.com>
Date:   Fri Nov 3 16:33:44 2023 +0000

    libstdc++: Remove redundant partial specialization in _Nth_type
    
    libstdc++-v3/ChangeLog:
    
            * include/bits/utility.h (_Nth_type): Remove redundant partial
            specialization.
    
    (cherry picked from commit ada871cfadd3f4960b4435f6f7f07a5aca1887d3)

Diff:
---
 libstdc++-v3/include/bits/utility.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/libstdc++-v3/include/bits/utility.h b/libstdc++-v3/include/bits/utility.h
index 714e2c02680..d7385ed72fd 100644
--- a/libstdc++-v3/include/bits/utility.h
+++ b/libstdc++-v3/include/bits/utility.h
@@ -250,10 +250,6 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
     { };
 
 #if ! __cpp_concepts // Need additional specializations to avoid ambiguities.
-  template<typename _Tp0, typename _Tp1, typename... _Rest>
-    struct _Nth_type<0, _Tp0, _Tp1, _Rest...>
-    { using type = _Tp0; };
-
   template<typename _Tp0, typename _Tp1, typename _Tp2, typename... _Rest>
     struct _Nth_type<0, _Tp0, _Tp1, _Tp2, _Rest...>
     { using type = _Tp0; };

                 reply	other threads:[~2023-11-08 13:18 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=20231108131840.7480E3858C5E@sourceware.org \
    --to=redi@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).