When I posted a request about allocators for the container library, I
received 2 answers.
I don't know about the recent one, but I know I've responded to previous
questions on that topic.
It's not a topic I am hugely invested in, just because I don't think a
container library is a good fit for the way I've usually seen C used, but
I think it's interesting, and I have certainly made suggestions about it.
Fundamentally, though, you're working on something that most of the people
here don't think they need, and you aren't saying things which are hilariously
over the top and obviously wrong. When you do say things which are obviously
wrong, you get more responses, but they're all corrections.
I suspect some of what you're seeing is inertia of various forms; most of us
already have or don't need a list library, for instance. I quite simply
can't comprehend when I'd end up wanting a "container". I can see when I
want lists, or when I want arrays, but I can't conceive of ever writing a
piece of code in which I want a container but don't care which of those it
is, or in which my choice of list or array would change. As a result, I
simply don't see "container" as a useful abstraction for writing code.
A similar design for, say, a hash library, which was unambiguously a library
for hashes and not for any other sort of thing, might be very interesting
to me, because I've not been especially happy with the hash libraries I've
seen.
-s