[PATCH] Avoid allocator operator== in _Safe_container
Jonathan Wakely
jwakely@redhat.com
Mon Aug 9 10:34:27 GMT 2021
On Mon, 9 Aug 2021 at 11:33, Jonathan Wakely wrote:
>
> On Mon, 9 Aug 2021 at 11:26, François Dumont via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
> >
> > Some newly introduced tests in
> > 23_containers/unordered_map/cons/default.cc revealed that we are forcing
> > the allocator type to have a operator==.
>
> All allocators are required to have operator== so that should not be a
> problem. What is the error?
OK, I see it. I just forgot to define operator== and operator!= for
the custom allocator in that new test, and that should be added.
More information about the Libstdc++
mailing list