> `lptabz` is more or less drop-in compatible with both sets & tables (both > ordered & unordered) and maybe more explicitly states up front that it is a > multiset/multitable which has caused quite a bit of confusion/surprise > (What!??! Dups in a hash?! The heck you say! Take it out!! They are now > deprecated in std/tables).
IMHO, it does make sense to keep `Table/Set` API separate from `MultiTable/MultiSet` in std lib. > I wouldn't mind, but Araq often says things like "the stdlib cannot keep up > with anything". One of the main Nim's selling points is the performance (both CPU and memory). Together with sequences hash tables are the most frequently used container data types. Having state of the art, cache-line friendly hash table implementation is the must have, IMHO.
