I think this is intentional, so the destructor lines up with the constructor, and we do it in a few places:

containers.tex: ~vector();
iostreams.tex: ~Init();
iostreams.tex: ~path();
iostreams.tex: ~file_status();
iostreams.tex: ~directory_entry();
iostreams.tex: ~directory_iterator();
iostreams.tex: ~recursive_directory_iterator();
iterators.tex: ~istream_iterator() = default;
iterators.tex: ~ostream_iterator();
locales.tex: ~numpunct_byname();
numerics.tex: ~mask_array();
numerics.tex: ~indirect_array();
strings.tex: ~basic_string();
utilities.tex: ~allocator();

That doesn't mean we have to keep it though.

we do it in a few places

Blech, I only looked at a couple which of course didn't use this device. It would be nice to pick a rule and be consistent throughout the standard. (See template< vs. template <)

I'll repush with them all fixed. (Yes, I said "fixed." I'm totally unbiased.)

containers.tex: ~vector();

The fact that vector<bool> uses this device clearly indicates that it's very, very wrong.

There's a consistent fix throughout.