Srđan Panić
Srđan Panić
Well `mem_free` and others are used by the structure internaly. The thing is that we can't guarantee that the data was allocated using the same allocators as was the structure....
> The documentation gives some hints that the default hashtable and hashset implementation are assuming C strings as keys. However, the "official" documentation use some defines that have been removed...
I'm not sure what we would gain from this. It would also break the test builds.
You make a good point. I guess that includes should be converted to angle bracket variants.
Hey, thanks for opening an issue :-) If I understand you correctly, you're saying that there should be a pointer to a `free` function kept in the hashtable structure that...
@flyxi121 It's definitely not by design. It should have been updated when `ARCH_64` was added, but apparently it was overlooked. Thanks for spotting it!
Yep, that's also a bug. It should be: ``` void **new_buff = ar->mem_alloc(ar->capacity * sizeof(void*)); ``` Again, thanks for eyeballing the code. These things are near impossible to catch with...
Sounds like a good idea.
The data is not copied by design. You can think of `list_add_all` as nothing more than `list_add` that adds pointers in bulk. And since **pointers are the data** that the...
Definitely, thanks for bringing it up. It was already discussed [here](https://github.com/srdja/Collections-C/issues/26).