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-425] libstdc++: Improve doxygen docs for std::pointer_traits Date: Fri, 13 May 2022 12:34:53 +0000 (GMT) [thread overview] Message-ID: <20220513123453.3C936395A40A@sourceware.org> (raw) https://gcc.gnu.org/g:757146fb1c82b49e78ee82c882677814f25c2429 commit r13-425-g757146fb1c82b49e78ee82c882677814f25c2429 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed May 11 16:13:16 2022 +0100 libstdc++: Improve doxygen docs for std::pointer_traits libstdc++-v3/ChangeLog: * include/bits/ptr_traits.h: Add some doxygen comments. Diff: --- libstdc++-v3/include/bits/ptr_traits.h | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/libstdc++-v3/include/bits/ptr_traits.h b/libstdc++-v3/include/bits/ptr_traits.h index 047efa5cf28..8360c3b6557 100644 --- a/libstdc++-v3/include/bits/ptr_traits.h +++ b/libstdc++-v3/include/bits/ptr_traits.h @@ -47,6 +47,8 @@ namespace std _GLIBCXX_VISIBILITY(default) { _GLIBCXX_BEGIN_NAMESPACE_VERSION + /// @cond undocumented + class __undefined; // For a specialization `SomeTemplate<T, Types...>` the member `type` is T, @@ -91,6 +93,8 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION using __ptr_traits_elem_t = typename __ptr_traits_elem<_Ptr>::type; #endif + /// @endcond + // Define pointer_traits<P>::pointer_to. template<typename _Ptr, typename _Elt, bool = is_void<_Elt>::value> struct __ptr_traits_ptr_to @@ -187,6 +191,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION /** * @brief Uniform interface to all pointer-like types + * @headerfile memory * @ingroup pointer_abstractions * @since C++11 */ @@ -203,6 +208,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION /** * @brief Partial specialization for built-in pointers. + * @headerfile memory * @ingroup pointer_abstractions * @since C++11 */
reply other threads:[~2022-05-13 12:34 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=20220513123453.3C936395A40A@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).