RandyGaul
RandyGaul
Like in my own serialization library (it's really similar to JSON), to support a dynamic array for the above example, it would just be like so (for step 3 in...
> Hmm, well I don't think you should store the bees in the beehive in this case ;) The beehive should probably just have a handle that goes into a...
Ah I definitely didn’t explain what I meant by “support std::vector” well enough. I meant to simply memcpy the POD data into the users array type, and potentially alloc the...
Oops. On my phone accidentally closed the issue lol
1. For dynamic arrays, yes, always allocate the array. 2. The dynamic would have a `count` member and a `capacity` member. Count is number of elements. Capacity is number of...
The more I think about it the more I think Simon's suggestion of using a wrapping API like a utility is the way to go. In this case, my questions...
With the current state of DL, here is the best solution I can think of. ```cpp const char* bees_and_hive = STRINGIFY({ "types" : { "bee_t" : { "members" : [...
@wc-duck that would grant support for one kind of dynamic array, and while I'm sure it would work well, it's not quite solving the problem I am interested in. What...
Yeah I don't see an easy way either, besides a special-case feature in `tld` for dynamic arrays.
I wrote cute_sound.h and would be happy to prototype a lightweight wrapper implementation. It's recently got some updates for high-perf pitch modulation, sort of rounding out the last major feature...