diff options
author | Peng Liu <winner245@hotmail.com> | 2024-11-13 05:08:08 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-11-13 11:08:08 +0100 |
commit | c7df10643bda4acdc9a02406a2eee8aa4ced747f (patch) | |
tree | e5b6bb7ef77562b6692ea26ef72b6e42e7866a8d /libcxx/src/filesystem/path.cpp | |
parent | 3e20bae827c0a314142fea74aa3d7ead039fab3d (diff) | |
download | llvm-c7df10643bda4acdc9a02406a2eee8aa4ced747f.zip llvm-c7df10643bda4acdc9a02406a2eee8aa4ced747f.tar.gz llvm-c7df10643bda4acdc9a02406a2eee8aa4ced747f.tar.bz2 |
Unify naming of internal pointer members in std::vector and std::__split_buffer (#115517)
Related to PR #114423, this PR proposes to unify the naming of the
internal pointer members in `std::vector` and `std::__split_buffer` for
consistency and clarity.
Both `std::vector` and `std::__split_buffer` originally used a
`__compressed_pair<pointer, allocator_type>` member named `__end_cap_`
to store an internal capacity pointer and an allocator. However,
inconsistent naming changes have been made in both classes:
- `std::vector` now uses `__cap_` and `__alloc_` for its internal
pointer and allocator members.
- In contrast, `std::__split_buffer` retains the name `__end_cap_` for
the capacity pointer, along with `__alloc_`.
This inconsistency between the names `__cap_` and `__end_cap_` has
caused confusions (especially to myself when I was working on both
classes). I suggest unifying these names by renaming `__end_cap_` to
`__cap_` in `std::__split_buffer`.
Diffstat (limited to 'libcxx/src/filesystem/path.cpp')
0 files changed, 0 insertions, 0 deletions