All GCs are prone to leak, including precise ones. The point of
garbage collection is not to prevent leaks, but rather to
prevent use-after-free bugs.
Of course I can have leaks in a GC environment, but having
non-deterministic leaks is another thing, and I'd rather make
sure to delete my ref
On Saturday, 4 February 2017 at 11:09:21 UTC, thedeemon wrote:
On Wednesday, 1 February 2017 at 06:58:43 UTC, osa1 wrote:
I'm wondering what
are the implications of the fact that current GC is a
Boehm-style conservative
GC rather than a precise one, I've never worked with a
conservative GC bef
On Friday, 3 February 2017 at 10:49:00 UTC, Kagamin wrote:
Leaks are likely in 32-bit processes and unlikely in 64-bit
processes. See e.g.
https://issues.dlang.org/show_bug.cgi?id=15723
This looks pretty bad. I think I'll consider something else until
D's memory management story gets better.
On Wednesday, 1 February 2017 at 09:40:17 UTC, Ola Fosheim
Grøstad wrote:
On Wednesday, 1 February 2017 at 06:58:43 UTC, osa1 wrote:
I'm wondering what
are the implications of the fact that current GC is a
Boehm-style conservative
GC rather than a precise one, I've never worked with a
conserva
Hi all,
I was looking at D as the next language to use in my hobby
projects, but the
"conservative GC" part in the language spec
(http://dlang.org/spec/garbage.html) looks a bit concerning. I'm
wondering what
are the implications of the fact that current GC is a Boehm-style
conservative
GC ra
