Interest in allocator interface support?

[VisenDev]

When writing my own c utilities library, I found using a (zig inspired) custom allocator system to be really useful. It lets you easily convert between using a leak checking allocator, a fixed buffer allocator, arena allocator, normal stdlib malloc, etc... really easily.

Example of what such an allocator interface looks like: https://github.com/VisenDev/pimbs/blob/master/src/allocator.h

From my understanding, stc currently only supports basic heap allocation. Supporting some sort of allocator interface like this would make it really easy for users to have much more fine grained control over memory.

Making this issue to see if this idea was of any interest to the stc devs

[polijan]

Custom allocators are important, and it's a good idea to support alternate allocators as easily as possible (perhaps even with a few builtin customizable allocators within STC itself in the future?). Fortunately, there are interesting possibilities already implemented in STC, such as ...

• If you #define your own c_malloc(sz), c_calloc(n, sz), c_realloc(ptr, old_sz, sz), c_free(ptr, sz) prior to including STC headers, then those will be used by STC.
• Also the #define i_allocator directive allows to specify a custom alternate allocator interface per container type. There is an example of that in the "container-instance customization" paragraph of the main README.