On Saturday, 6 March 2021 at 20:45:00 UTC, Adam D. Ruppe wrote:
> On Saturday, 6 March 2021 at 20:21:41 UTC, Rumbu wrote:
>> It seems that the author failed to update himself or - what's worse - wants to justify D failure in having deterministic class destruction by pointing to others.
>
> D *does* have deterministic class destruction. `scope Object o = new Object;`. Also `scope(exit) .destroy(o);`.

Be warned that there is currently a bug where even `scope C c = new C;` will not actually call the destructor for extern(C++) classes:
    https://issues.dlang.org/show_bug.cgi?id=21693

There doesn't seem to be any fundamental reason for this, though; it's just an oversight that will hopefully be fixed soon.

On Sunday, 7 March 2021 at 07:10:30 UTC, Rumbu wrote:

> Secondly, basic language constructs must be available in the core language not in a library, even if it's just druntime in this case. Putting them in the library makes the language unusable without that library.

FYI, there are a bunch of language features that require library support. One of the most obvious ones would be allocating memory using `new`.

--
/Jacob Carlborg

This is against that the D GC competes with:

https://malloc.se/blog/zgc-jdk16

Maximum: 1ms pause for the new Java GC (zgc)

On Tuesday, 23 March 2021 at 23:12:22 UTC, rsy wrote:
> This is against that the D GC competes with:
>
> https://malloc.se/blog/zgc-jdk16
>
> Maximum: 1ms pause for the new Java GC (zgc)

That is just one of many options on the Java world, there is also Azul, while PTC and Aicas have real-time ones, deployed into production including military weapons systems in battleships and missile radar controls, where a GC pause in the wrong moment is a no-go.