public inbox for gcc-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-9484] libstdc++: Fix typo in doxygen comment Date: Thu, 27 Apr 2023 14:43:43 +0000 (GMT) [thread overview] Message-ID: <20230427144343.EEEA4385828D@sourceware.org> (raw) https://gcc.gnu.org/g:8aa615e0230cc73bd06281dddb187d371a6d2824 commit r12-9484-g8aa615e0230cc73bd06281dddb187d371a6d2824 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Apr 26 23:38:43 2023 +0100 libstdc++: Fix typo in doxygen comment libstdc++-v3/ChangeLog: * include/bits/mofunc_impl.h: Fix typo in doxygen comment. (cherry picked from commit 481281ccf41aa2bc596e548edaad4e57833f3340) Diff: --- libstdc++-v3/include/bits/mofunc_impl.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/libstdc++-v3/include/bits/mofunc_impl.h b/libstdc++-v3/include/bits/mofunc_impl.h index 47e1e506306..318a55e618f 100644 --- a/libstdc++-v3/include/bits/mofunc_impl.h +++ b/libstdc++-v3/include/bits/mofunc_impl.h @@ -51,14 +51,13 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION * @headerfile functional * * The `std::move_only_function` class template is a call wrapper similar - * to * `std::function`, but does not require the stored target function + * to `std::function`, but does not require the stored target function * to be copyable. * * It also supports const-qualification, ref-qualification, and * no-throw guarantees. The qualifications and exception-specification * of the `move_only_function::operator()` member function are respected * when invoking the target function. - * */ template<typename _Res, typename... _ArgTypes, bool _Noex> class move_only_function<_Res(_ArgTypes...) _GLIBCXX_MOF_CV
reply other threads:[~2023-04-27 14:43 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=20230427144343.EEEA4385828D@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).