public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Tamar Christina <tnfchris@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/ARM/heads/arm-struct-reorg-wip)] libstdc++: Fix non-ASCII characters in comment Date: Fri, 17 Jul 2020 12:44:15 +0000 (GMT) [thread overview] Message-ID: <20200717124415.B9C08393BC35@sourceware.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1607 bytes --] https://gcc.gnu.org/g:97a7c22955435c0466ea96c6d77d2a71b2ae1277 commit 97a7c22955435c0466ea96c6d77d2a71b2ae1277 Author: Jonathan Wakely <jwakely@redhat.com> Date: Sun Feb 9 13:54:32 2020 +0000 libstdc++: Fix non-ASCII characters in comment * include/std/ranges: Fix non-ASCII characters in comment. Diff: --- libstdc++-v3/ChangeLog | 2 ++ libstdc++-v3/include/std/ranges | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index fb4641aee6d..cc23523f57a 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,5 +1,7 @@ 2020-02-09 Jonathan Wakely <jwakely@redhat.com> + * include/std/ranges: Fix non-ASCII characters in comment. + * include/bits/range_cmp.h (__detail::__eq_builtin_ptr_cmp): Require equality comparison to be valid and return bool. (__detail::__less_builtin_ptr_cmp): Likewise for less-than comparison. diff --git a/libstdc++-v3/include/std/ranges b/libstdc++-v3/include/std/ranges index 891ecf75eff..970e904bddd 100644 --- a/libstdc++-v3/include/std/ranges +++ b/libstdc++-v3/include/std/ranges @@ -2590,8 +2590,8 @@ namespace views // XXX: [24.7.11.3.1] // Many of the following specifications refer to the notional member - // current of outer-iterator. current is equivalent to current_ if - // V models forward_range, and parent_->current_ otherwise. + // current of outer-iterator. current is equivalent to current_ if + // V models forward_range, and parent_->current_ otherwise. constexpr auto& __current() {
reply other threads:[~2020-07-17 12:44 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=20200717124415.B9C08393BC35@sourceware.org \ --to=tnfchris@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: 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).