On Mon, 9 Aug 2021 at 11:34, Jonathan Wakely wrote: > > On Mon, 9 Aug 2021 at 11:33, Jonathan Wakely wrote: > > > > On Mon, 9 Aug 2021 at 11:26, François Dumont via Libstdc++ > > 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. Fixed like this instead. Tested x86_64-linux with -D_GLIBCXX_DEBUG. Pushed to trunk.