Le dim. 24 nov. 2019 à 11:53, Ludovic Courtès a écrit :
>
> Hello!
>
> A few days ago David was explaining on #guile how ‘bytevector->pointer’
> was generating too much garbage for his use case. An idea we came up
> with was to embed the pointer object in the bytevector.
I would be very happy to
Le dim. 24 nov. 2019 à 18:54, Ludovic Courtès a écrit :
>
> Hello!
>
> It seems that if you ‘set!’ a public variable of a declarative module,
> the change is visible to all the module users, but it’s not necessarily
> visible to procedures within that module, presumably because they use an
> inlin
Hello!
It seems that if you ‘set!’ a public variable of a declarative module,
the change is visible to all the module users, but it’s not necessarily
visible to procedures within that module, presumably because they use an
inlined or specialized variant of that thing.
I would have imagined that p
Hello!
A few days ago David was explaining on #guile how ‘bytevector->pointer’
was generating too much garbage for his use case. An idea we came up
with was to embed the pointer object in the bytevector.
The patch below does that but it leads to segfaults because I’m guessing
there’s generated b
