Tasks, actors and garbage collection

[jmh530]

On Tuesday, 20 April 2021 at 09:52:07 UTC, Ola Fosheim Grøstad 
wrote:
> [snip]
> It seems to me that the obvious way to retain the easy of use 
> that garbage collection provides without impeding performance 
> is to limit the memory to scan, and preferably do the scanning 
> when nobody is using the memory.
>
> The actor model seems to be a good fit. Or call it a task, if 
> you wish. If each actor/task has it's own GC pool then there is 
> less memory to scan, and you can do the scanning when the 
> actor/task is waiting on I/O or scheduling. So you would get 
> less intrusive scanning pauses. It would also fit well with 
> async-await/futures.
>
> [snip]

Are you familiar with this:
https://github.com/hsutter/gcpp

How similar are these ideas?