Per thread heap, GC, etc.
IGotD-
nise at nise.com
Fri May 14 15:37:22 UTC 2021
On Friday, 14 May 2021 at 13:48:12 UTC, Markk wrote:
> Hi,
>
> [...]
>
> _Mark
I'm very much against binding any dynamic memory to any thread.
It collides with a lot of programming models. For example threads
created outside D, in C++ or any other language has no knowledge
of D GC memory. This means that FFI is much more complicated.
Also threads are like prostitutes, they do the work of the client
and then another client comes along doing some other work.
Typically example are thread pools where any thread can do any
work. Also bring fibers into the equation makes this even more
unfitting.
Memory bounded to a thread is a bad idea and as time moves on it
becomes more clear that a program should not assume which thread
they are running (should only operate on self) and also not which
CPU they are running on.
More information about the Digitalmars-d
mailing list