On Tuesday, 5 July 2022 at 12:34:57 UTC, ryuukk_ wrote:
On Monday, 4 July 2022 at 05:30:10 UTC, Andrej Mitrovic wrote:
On Sunday, 3 July 2022 at 08:46:31 UTC, Mike Parker wrote:
You can find the final draft of the high-level goals for the
D programming language at the following link:
https://github.com/dlang/vision-document
Under 'Memory safety':
Allow the continued use of garbage collection as the default
memory management strategy without impact. The GC is one of
D's strengths, and we should not "throw the baby out with the
bath water".
Under 'Phobos and DRuntime':
@nogc as much as possible.
Aren't these the polar opposites of each other? The GC is one
of D's strengths, yet we should avoid it as much as possible
in the standard library.
Then it's not part of D's strengths.
GC is one of D's strength because it is optional, not making
core APIs bing-your-own-memory-allocation-strategy through nogc
or allocators, is making it no longer optional, which is no
longer a strength imo
You don't want GC when you do microcontroller development, so
as a result core APIs (most of them) becomes useless, moving
forward that should make the story better for everyone
Which becomes a strength again
Feel free to consider it a strength, when in reality it is a flaw
against established market players.
https://www.microej.com/
https://www.wildernesslabs.co/
https://www.ptc.com/en/products/developer-tools/perc
https://www.aicas.com/wp/products-services/jamaicavm/
https://www.astrobe.com/
