Re: GUILE 2/3 and string encoding cost

[David Kastrup]

Han-Wen Nienhuys <address@hidden> writes:

> On Fri, Jan 24, 2020 at 10:51 AM David Kastrup <address@hidden> wrote:
>
>>
>> >> On a 64bit application, this would be somewhat more tenable, but we'd
>> >> need to override operator new for smobs.
>> >>
>> >> Or do we?  Maybe the heap is collected by default, and we need to switch
>> >> that off?
>> >>
>> >>
>> > 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.
>>
>
> Did we ever try this and publish results?

No.  Since much of LilyPond's data containing SCM values is stored in
STL containers, it would require serious messing with allocators to get
there.

-- 
David Kastrup