Re: Resurrecting top-notch continuous integration for Guile

Hi! Ludovic Courtès skribis: > There’s still much tweaking we can do, but the basics are in place, and > I find it pretty cool. :-) If there are no objections, I’ll merge this > branch into “main”. It’s going to be nice to have a dashboard to look > at before the next release! Merged in Guil

[RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized

Hello Guile hackers. We are in the process of integrating GNU poke[1] in GDB by mean of libpoke. Problem is, libpoke uses the Boehm GC, as guile does. We are working on switching to an ad-hoc exact collector, but it will get some time. So, in the interim, we may: 1) Make both libguile and li

Re: Resurrecting top-notch continuous integration for Guile

Hi! Ludovic Courtès writes: > Hi! > > Ludovic Courtès skribis: > >> There’s still much tweaking we can do, but the basics are in place, and >> I find it pretty cool. :-) If there are no objections, I’ll merge this >> branch into “main”. It’s going to be nice to have a dashboard to look >> at

Re: [RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized

On 06/02/2023 19:34, Jose E. Marchesi wrote: > > Hello Guile hackers. > > We are in the process of integrating GNU poke[1] in GDB by mean of > libpoke. > > Problem is, libpoke uses the Boehm GC, as guile does. We are working on > switching to an ad-hoc exact collector, but it will get some time

Re: [RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized

> On 06/02/2023 19:34, Jose E. Marchesi wrote: >> >> Hello Guile hackers. >> >> We are in the process of integrating GNU poke[1] in GDB by mean of >> libpoke. >> >> Problem is, libpoke uses the Boehm GC, as guile does. We are working on >> switching to an ad-hoc exact collector, but it will g