From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Fix Doxygen warning
Date: Sat, 19 Nov 2022 15:08:40 +0000 [thread overview]
Message-ID: <20221119150840.1673902-1-jwakely@redhat.com> (raw)
Tested x86_64-linux. Pushed to trunk.
-- >8 --
This fixes a Doxygen warning about a mismatched parameter name. The
standard uses 'r' here, like the Doxygen comment, so use '__r' instead
of '__e'.
libstdc++-v3/ChangeLog:
* include/bits/ptr_traits.h (pointer_traits::pointer_to): Rename
parameter.
---
libstdc++-v3/include/bits/ptr_traits.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/libstdc++-v3/include/bits/ptr_traits.h b/libstdc++-v3/include/bits/ptr_traits.h
index 71370ff4fc9..b46a1ac34c9 100644
--- a/libstdc++-v3/include/bits/ptr_traits.h
+++ b/libstdc++-v3/include/bits/ptr_traits.h
@@ -104,17 +104,17 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
/**
* @brief Obtain a pointer to an object
* @param __r A reference to an object of type `element_type`
- * @return `pointer::pointer_to(__e)`
- * @pre `pointer::pointer_to(__e)` is a valid expression.
+ * @return `pointer::pointer_to(__r)`
+ * @pre `pointer::pointer_to(__r)` is a valid expression.
*/
static pointer
- pointer_to(element_type& __e)
+ pointer_to(element_type& __r)
#if __cpp_lib_concepts
requires requires {
- { pointer::pointer_to(__e) } -> convertible_to<pointer>;
+ { pointer::pointer_to(__r) } -> convertible_to<pointer>;
}
#endif
- { return pointer::pointer_to(__e); }
+ { return pointer::pointer_to(__r); }
};
// Do not define pointer_traits<P>::pointer_to if element type is void.
--
2.38.1
reply other threads:[~2022-11-19 15:08 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=20221119150840.1673902-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).