-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[NFC][libc++] Fix typo in libcxx/include/__memory/pointer_traits.h
#157304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
vinay-deshmukh
commented
Sep 6, 2025
- Apply the typo fix as a separate NFC patch from here: https://github.com/llvm/llvm-project/pull/134330/files#r2313015079
libcxx/include/__memory/pointer_traits.h
libcxx/include/__memory/pointer_traits.h
|
@llvm/pr-subscribers-libcxx Author: Vinay Deshmukh (vinay-deshmukh) Changes
Full diff: https://github.com/llvm/llvm-project/pull/157304.diff 1 Files Affected:
diff --git a/libcxx/include/__memory/pointer_traits.h b/libcxx/include/__memory/pointer_traits.h
index 8c7f8dff1b76b..62fcd93263b02 100644
--- a/libcxx/include/__memory/pointer_traits.h
+++ b/libcxx/include/__memory/pointer_traits.h
@@ -255,7 +255,7 @@ concept __resettable_smart_pointer_with_args = requires(_Smart __s, _Pointer __p
// This function ensures safe conversions between fancy pointers at compile-time, where we avoid casts from/to
// `__void_pointer` by obtaining the underlying raw pointer from the fancy pointer using `std::to_address`,
// then dereferencing it to retrieve the pointed-to object, and finally constructing the target fancy pointer
-// to that object using the `std::pointer_traits<>::pinter_to` function.
+// to that object using the `std::pointer_traits<>::pointer_to` function.
template <class _PtrTo, class _PtrFrom>
_LIBCPP_CONSTEXPR_SINCE_CXX20 _LIBCPP_HIDE_FROM_ABI _PtrTo __static_fancy_pointer_cast(const _PtrFrom& __p) {
using __ptr_traits = pointer_traits<_PtrTo>;
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now.
@philnik777 If #152989 won't be resolved soon, I think we should at least merge this.
@vinay-deshmukh Could you make your e-mail address public according to our general convention? |
I've pushed a new commit with the correct email address. let me know if that works or if I need to rebase/edit all existing commits. P.S. I don't have "merge" permissions, so will need a reviewer to merge the change for me as well... |
I think you should set your GitHub account to make the email address public. |
Maybe that setting does not affect the commits that are not already pushed? |
@vinay-deshmukh The merge E-Mail is important. It's correct now. |