[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GUILE 2/3 and string encoding cost
From: |
Han-Wen Nienhuys |
Subject: |
Re: GUILE 2/3 and string encoding cost |
Date: |
Fri, 24 Jan 2020 13:03:50 +0100 |
On Fri, Jan 24, 2020 at 10:51 AM David Kastrup <address@hidden> wrote:
>
> > What do you mean with "heap is collected"?
>
> "Collected" is probably the wrong expression. Sweeped and marked. The
> proposed behavior by Guile developers is not to bother with individual
> mark hooks and just let the whole heap be marked and sweeped.
>
what is the documented way of disabling the hooks? And are we supposed to
include the BGC headers ourselves and issue GC_blah commands directly?
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
- Re: GUILE 2/3 and string encoding cost, (continued)
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, Han-Wen Nienhuys, 2020/01/24
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24
- Re: GUILE 2/3 and string encoding cost,
Han-Wen Nienhuys <=
- Re: GUILE 2/3 and string encoding cost, David Kastrup, 2020/01/24