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++/100768] Range iterator operations should be function objects
Date: Wed, 02 Jun 2021 13:43:32 +0000	[thread overview]
Message-ID: <bug-100768-4-dPwOHiANS8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100768-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100768

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

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

commit r11-8501-gf2b76257e9a487fd2c7265094f7b4d1bd46f5f03
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed May 26 17:32:53 2021 +0100

    libstdc++: Change [range.iter.op] functions to function objects [PR 100768]

    The standard specifies std::ranges::distance etc as function templates,
    but it also requires them to not be found by ADL, and to suppress ADL
    when normal unqualified lookup does find them. That means they need to
    be function objects.

    libstdc++-v3/ChangeLog:

            PR libstdc++/100768
            * include/bits/ranges_base.h (advance, distance, next, prev):
            Replace function templates with function objects.
            * testsuite/24_iterators/headers/iterator/synopsis_c++20.cc:
            Adjust for changes to function objects.
            * testsuite/std/ranges/adaptors/elements.cc: Add using
            declarations for names from namespace ranges.
            * testsuite/std/ranges/adaptors/transform.cc: Likewise.
            * testsuite/24_iterators/range_operations/100768.cc: New test.

    (cherry picked from commit a49a045b92f982f5617c3bbde97a33157237e25b)

  parent reply	other threads:[~2021-06-02 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 12:06 [Bug libstdc++/100768] New: " rs2740 at gmail dot com
2021-05-26 13:37 ` [Bug libstdc++/100768] " redi at gcc dot gnu.org
2021-05-26 18:40 ` cvs-commit at gcc dot gnu.org
2021-06-02 13:43 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-03 14:57 ` cvs-commit at gcc dot gnu.org
2021-06-03 14:58 ` redi 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-100768-4-dPwOHiANS8@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).