On 07.08.2021 23:19, to...@tuxteam.de wrote:
> On Sat, Aug 07, 2021 at 12:31:09PM +0200, Taylan Kammer wrote:
>> One consideration is how this should behave in the case of
>> bytevectors that were created from an FFI pointer [...]
>
> Hm. I don't understand. Realloc /may/ return a different pointe
I will start the development of stis-engine that is based on fibers and
will experiment with applications that separate into different network
components.
Among things I plan to add serializers, deserializers, zipping and zero mq
networking that works
with fibers. E.g. we will stream things with f
Thank you for your responses Taylan and Maxime!
My initial reaction to the concern about multithreaded code is similar
to Taylan. I'm not sure if Guile has multithreading concepts built into
the compiler. If so, one can only check the length again after a mutex.
Appreciate the malloc, realloc, an