[llvm-bugs] [Bug 50299] Bogus warnings: warning: 'allocator<void>' is deprecated

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=50299

Louis Dionne <ldionne at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED
 Fixed By Commit(s)|                            |87784cc6fb3453a17e0e7826b94
                   |                            |3a1d93cbfeccf

--- Comment #7 from Louis Dionne <ldionne at apple.com> ---
commit 87784cc6fb3453a17e0e7826b943a1d93cbfeccf
Author: Louis Dionne <ldionne.2 at gmail.com>
Date:   Tue Jun 15 16:08:38 2021 -0400

    [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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20210616/74df128d/attachment.html>