diff options
| author | Louis Dionne <ldionne.2@gmail.com> | 2021-06-15 16:08:38 -0400 |
|---|---|---|
| committer | Louis Dionne <ldionne.2@gmail.com> | 2021-06-16 09:54:29 -0400 |
| commit | 87784cc6fb3453a17e0e7826b943a1d93cbfeccf (patch) | |
| tree | 05996e60372f1e72ba60803d7a0f070eee1582fc /llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp | |
| parent | 70b37f4c03cd189c94167dc22d9f5303c8773092 (diff) | |
| download | llvm-87784cc6fb3453a17e0e7826b943a1d93cbfeccf.zip llvm-87784cc6fb3453a17e0e7826b943a1d93cbfeccf.tar.gz llvm-87784cc6fb3453a17e0e7826b943a1d93cbfeccf.tar.bz2 | |
[libc++] Undeprecate the std::allocator<void> specialization
While the std::allocator<void> specialization was deprecated by
https://wg21.link/p0174#2.2, the *use* of std::allocator<void> by users
was not. The intent was that std::allocator<void> could still be used
in C++17 and C++20, but starting with C++20 (with the removal of the
specialization), std::allocator<void> would use the primary template.
That intent was called out in wg21.link/p0619r4#3.9.
As a result of this patch, _LIBCPP_ENABLE_CXX20_REMOVED_ALLOCATOR_MEMBERS
will also not control whether the explicit specialization is provided or
not. It shouldn't matter, since in C++20, one can simply use the primary
template.
Fixes http://llvm.org/PR50299
Differential Revision: https://reviews.llvm.org/D104323
Diffstat (limited to 'llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp')
0 files changed, 0 insertions, 0 deletions