Has a much more C-style syntax, except much more refined from the years of hindsight. The catch? No corporate backing, didn't jump on the "immutable by default" trend when functional programming evangelists said for loops are a bad practice and instead we should just write recursive functions as a workaround, memory safety is opt-in (although "safe by default" can be done by starting your files with @safe:), some of the lead devs are "naive centrists" who want to "give everyone a chance at coding even if they're bad people (nazis)", implementing new changes to the lang has slowed down significantly up until the departure of Adam D Ruppe and the drama surrounding it, etc.
"safe by default" can be done by starting your files with @safe:
Last time I heard about that it was much more limited than Rust, for example it even disallowed taking references to local variables. Has something changed since then?
D has many memory safety features. For local variables, one should use pointers, otherwise ref does references that are guaranteed to be valid to their lifetime, and thus have said limitations.
For local variables, one should use pointers, otherwise ref does references that are guaranteed to be valid to their lifetime, and thus have said limitations.
Should I take this to mean that pointers instead are not guaranteed to be valid, and thus are not memory safe?
Pointers are not guaranteed to be safe. DIP1000 was supposed to solve the issue of a pointer referencing to a now expired variable (see example below), but it's being replaced by something else instead.
int* p;
{
int q = 42;
p = &q;
}
writeln(*p); //ERROR: This will cause memory leakage, due to q no longer existing
Pointers are not guaranteed to be safe
So I guess they are forbidden in @safe mode?
but it's being replaced by something else instead
Do you know what is the replacement? I tried looking up DIP1000 but it only says "superceded" without mentioning by what.
This makes me wonder how ready D is for someone that wants to extensively use @safe though.
That's why I often recommend D instead.
Has a much more C-style syntax, except much more refined from the years of hindsight. The catch? No corporate backing, didn't jump on the "immutable by default" trend when functional programming evangelists said
forloops are a bad practice and instead we should just write recursive functions as a workaround, memory safety is opt-in (although "safe by default" can be done by starting your files with@safe:), some of the lead devs are "naive centrists" who want to "give everyone a chance at coding even if they're bad people (nazis)", implementing new changes to the lang has slowed down significantly up until the departure of Adam D Ruppe and the drama surrounding it, etc.Last time I heard about that it was much more limited than Rust, for example it even disallowed taking references to local variables. Has something changed since then?
D has many memory safety features. For local variables, one should use pointers, otherwise
refdoes references that are guaranteed to be valid to their lifetime, and thus have said limitations.Should I take this to mean that pointers instead are not guaranteed to be valid, and thus are not memory safe?
Pointers are not guaranteed to be safe. DIP1000 was supposed to solve the issue of a pointer referencing to a now expired variable (see example below), but it's being replaced by something else instead.
So I guess they are forbidden in
@safemode?Do you know what is the replacement? I tried looking up DIP1000 but it only says "superceded" without mentioning by what.
This makes me wonder how ready D is for someone that wants to extensively use
@safethough.https://github.com/ZILtoid1991/newxml/tree/main
This XML parser of mine uses safe by default.
It also seems to require a GC though...