[all-commits] [llvm/llvm-project] 397707: [libc++] __uglify non-conforming member typedef `b...
A. Jiang via All-commits
all-commits at lists.llvm.org
Fri Oct 18 08:27:33 PDT 2024
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 397707f7188b6df52de1cff85e08e64e3ee5acc3
https://github.com/llvm/llvm-project/commit/397707f7188b6df52de1cff85e08e64e3ee5acc3
Author: A. Jiang <de34 at live.cn>
Date: 2024-10-18 (Fri, 18 Oct 2024)
Changed paths:
M libcxx/docs/ReleaseNotes/20.rst
M libcxx/include/bitset
M libcxx/include/forward_list
M libcxx/include/list
M libcxx/test/std/containers/sequences/forwardlist/types.pass.cpp
M libcxx/test/std/containers/sequences/list/types.pass.cpp
M libcxx/test/std/utilities/template.bitset/bitset.members/nonstdmem.uglified.compile.pass.cpp
Log Message:
-----------
[libc++] __uglify non-conforming member typedef `base` (#112843)
Currently, libc++'s `bitset`, `forward_list`, and `list` have
non-conforming member typedef name `base`. The typedef is private, but
can cause ambiguity in name lookup.
Some other classes in libc++ that are either implementation details or
not precisely specified by the standard also have member typdef `base`.
I think this can still be conforming.
Follows up #80706 and #111127.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list