[Bug libstdc++/103162] overconstrained std::pmr::memory_resource allocate/deallocate methods

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103162

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The committee's view is that this function should not be able to return a null
pointer because you can't store objects there (so if that's not true for your
environment, use -fno-delete-null-pointer-checks to inform the compiler of your
special case).

I will create a library issue to fix the wording in the standard, to make the
semantics clear (without the misleading reference to the storage returned by
allocation functions).