aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/SmallVector.cpp
diff options
context:
space:
mode:
authorArthur O'Dwyer <arthur.j.odwyer@gmail.com>2020-11-27 11:02:06 -0500
committerArthur O'Dwyer <arthur.j.odwyer@gmail.com>2020-12-01 22:13:39 -0500
commitd586f92c9456a972ee475a021525c0522b89587b (patch)
tree2f66cb796e5b2918a1f7aebb32b08db55f3c1232 /llvm/lib/Support/SmallVector.cpp
parent40950a44b9a6aefe17b130e291f8728b34844bce (diff)
downloadllvm-d586f92c9456a972ee475a021525c0522b89587b.zip
llvm-d586f92c9456a972ee475a021525c0522b89587b.tar.gz
llvm-d586f92c9456a972ee475a021525c0522b89587b.tar.bz2
[libc++] Consistently replace `std::` qualification with `_VSTD::` or nothing. NFCI.
I used a lot of `git grep` to find places where `std::` was being used outside of comments and assert-messages. There were three outcomes: - Qualified function calls, e.g. `std::move` becomes `_VSTD::move`. This is the most common case. - Typenames that don't need qualification, e.g. `std::allocator` becomes `allocator`. Leaving these as `_VSTD::allocator` would also be fine, but I decided that removing the qualification is more consistent with existing practice. - Names that specifically need un-versioned `std::` qualification, or that I wasn't sure about. For example, I didn't touch any code in <atomic>, <math.h>, <new>, or any ext/ or experimental/ headers; and I didn't touch any instances of `std::type_info`. In some deduction guides, we were accidentally using `class Alloc = typename std::allocator<T>`, despite `std::allocator<T>`'s type-ness not being template-dependent. Because `std::allocator` is a qualified name, this did parse as we intended; but what we meant was simply `class Alloc = allocator<T>`. Differential Revision: https://reviews.llvm.org/D92250
Diffstat (limited to 'llvm/lib/Support/SmallVector.cpp')
0 files changed, 0 insertions, 0 deletions