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-1367] libstdc++: Fix comment typos Date: Thu, 30 Jun 2022 15:12:13 +0000 (GMT) [thread overview] Message-ID: <20220630151213.5B9923841894@sourceware.org> (raw) https://gcc.gnu.org/g:c1fe8ddf6847a14152668064f163a2585e9dc894 commit r13-1367-gc1fe8ddf6847a14152668064f163a2585e9dc894 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Jun 30 11:28:23 2022 +0100 libstdc++: Fix comment typos libstdc++-v3/ChangeLog: * include/bits/utility.h: Fix comment typos. Diff: --- libstdc++-v3/include/bits/utility.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/libstdc++-v3/include/bits/utility.h b/libstdc++-v3/include/bits/utility.h index 4a457afcc1e..e0e40309a6d 100644 --- a/libstdc++-v3/include/bits/utility.h +++ b/libstdc++-v3/include/bits/utility.h @@ -125,7 +125,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION } // The standard says this macro and alias template should be in <tuple> but we -// we define them here, to be available in <array>, <utility> and <ranges> too. +// define them here, to be available in <array>, <utility> and <ranges> too. // _GLIBCXX_RESOLVE_LIB_DEFECTS // 3378. tuple_size_v/tuple_element_t should be available when // tuple_size/tuple_element are @@ -190,7 +190,6 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION #if __cplusplus >= 201703L - // struct in_place_t { explicit in_place_t() = default; };
reply other threads:[~2022-06-30 15:12 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=20220630151213.5B9923841894@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: 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).