On Monday, 9 May 2022 at 00:32:33 UTC, Ali Çehreli wrote:
On 5/8/22 17:25, H. S. Teoh wrote:
> somebody should make a dmd
> fork that introduces write barriers, plus a generational GC
(even if
> it's a toy, proof-of-concept-only implementation) to see if
the
> performance hit is really as bad as believed to be.
Ooh! DConf is getting even more interesting. :o)
Ali
A helpful paper: "Getting to Go: The Journey of Go's garbage
collector".
Positive highlights: 1) non-copying 2) no read barriers
Less friendly: 1) write barriers 2) GC aware fiber scheduler 3)
other???
Would be some (huge amount?) of work but porting/enabling an
opt-in golang latency GC could be a big enabler for the
casual/soft "real time" crowd.
Here's a link to the paper:
https://go.dev/blog/ismmkeynote
