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 r12-3879] libstdc++: Remove redundant 'inline' specifiers
Date: Fri, 24 Sep 2021 14:47:03 +0000 (GMT)	[thread overview]
Message-ID: <20210924144703.E7BFC3858402@sourceware.org> (raw)

https://gcc.gnu.org/g:9b11107ed72ca543af41dbb3226e16b61d31b098

commit r12-3879-g9b11107ed72ca543af41dbb3226e16b61d31b098
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Sep 24 11:30:59 2021 +0100

    libstdc++: Remove redundant 'inline' specifiers
    
    These functions are constexpr, which means they are implicitly inline.
    
    Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
    
    libstdc++-v3/ChangeLog:
    
            * include/bits/range_access.h (cbegin, cend): Remove redundant
            'inline' specifier.

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

diff --git a/libstdc++-v3/include/bits/range_access.h b/libstdc++-v3/include/bits/range_access.h
index ab2d4f8652c..3dec687dd94 100644
--- a/libstdc++-v3/include/bits/range_access.h
+++ b/libstdc++-v3/include/bits/range_access.h
@@ -122,7 +122,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
    */
   template<typename _Container>
     [[__nodiscard__]]
-    inline constexpr auto
+    constexpr auto
     cbegin(const _Container& __cont) noexcept(noexcept(std::begin(__cont)))
       -> decltype(std::begin(__cont))
     { return std::begin(__cont); }
@@ -134,7 +134,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
    */
   template<typename _Container>
     [[__nodiscard__]]
-    inline constexpr auto
+    constexpr auto
     cend(const _Container& __cont) noexcept(noexcept(std::end(__cont)))
       -> decltype(std::end(__cont))
     { return std::end(__cont); }


                 reply	other threads:[~2021-09-24 14:47 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=20210924144703.E7BFC3858402@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).