l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>
>> One potential issue that has been troubling me is that in Guile's model,
>> there's no guarantee that a module will _ever_ finish loading.
>
> I think the fact that we evaluate all the top-level forms is
> problematic. The R6RS
Mark H Weaver skribis:
> Andy Wingo writes:
>
>> In many ways I think Ludovic was right in #15602 -- we should allow
>> excursions to isolate changes to the module tree. Sometimes you want an
>> excursion to never add a module to the tree. Sometimes you do, but
>> maybe all in one go and with
Andy Wingo writes:
> In many ways I think Ludovic was right in #15602 -- we should allow
> excursions to isolate changes to the module tree. Sometimes you want an
> excursion to never add a module to the tree. Sometimes you do, but
> maybe all in one go and with a mutex, to avoid races -- like,
In many ways I think Ludovic was right in #15602 -- we should allow
excursions to isolate changes to the module tree. Sometimes you want an
excursion to never add a module to the tree. Sometimes you do, but
maybe all in one go and with a mutex, to avoid races -- like, you could
load a file or eva
As far as I can tell the make-fresh-user-module procedure is not called
by guile itself, and providing a global mutex for it with a binding
enabling it to be called from scheme code seems to work fine.
This also makes it straightforward to incorporate in a thread-safe
way the code you suggested to
On Sun, 07 Dec 2014 03:07:43 -0500
Mark H Weaver wrote:
> Chris Vine writes:
>
> > The make-fresh-user-module procedure leaks memory in guile-2.0.11 as
> > demonstrated by the attached test case. [...]
> >
> > The question which might be asked is "Would any sane person ever
> > want to invoke t
Chris Vine writes:
> The make-fresh-user-module procedure leaks memory in guile-2.0.11 as
> demonstrated by the attached test case. [...]
>
> The question which might be asked is "Would any sane person ever want
> to invoke the make-fresh-user-module procedure more than a few times
> in a practi
The make-fresh-user-module procedure leaks memory in guile-2.0.11 as
demonstrated by the attached test case. This test case should be
invoked either with the "shared" or "fresh" option. If invoked with
the "fresh" option, it will call make-fresh-user-module on each
iteration through the loop. On
