Re:What If C++ Abandoned Backward Compatibility?
by amelius on Saturday March 28, 2020 @06:23AM
(#22710305)
You would get D ...
[ Parent
| on HN ]
Re:What If C++ Abandoned Backward Compatibility?
by ComputerGuru on Saturday March 28, 2020 @08:14AM
(#22710658)
You would get a runtime and GC?
Re:What If C++ Abandoned Backward Compatibility?
by AH2mdte8kPnJS on Saturday March 28, 2020 @12:45PM
(#22712300)
D is able to run without its runtime and GC.
https://dlang.org/spec/betterc.html
And an older link:
https://www.auburnsounds.com/blog/2016-11-10_Running-D-witho...
Re:What If C++ Abandoned Backward Compatibility?
by roca on Saturday March 28, 2020 @03:54PM
(#22713859)
Able to run, yes. But it is not the default, ergonomic way to write D code like it is in C, C++ and Rust.
Re:What If C++ Abandoned Backward Compatibility?
by pjmlp on Saturday March 28, 2020 @06:44PM
(#22714859)
Thankfully, GC offers productivity and allows for safe code by default, while D still offers the necessary language features to do all the low level tricks from C, C++, Rust, Objective-C, if one actually needs to go down that level.
Re:What If C++ Abandoned Backward Compatibility?
by roca on Monday March 30, 2020 @06:42PM
(#22732950)
I like being able to write safe and GC-free code by default. Rust would be even better if it was possible to opt into GC, but I would still want to to be GC-free by default. It's good that the entire library ecosystem has grown up GC-free and that should continue.
Re:What If C++ Abandoned Backward Compatibility?
by ComputerGuru on Sunday March 29, 2020 @02:27AM
(#22716856)
If I hadn’t already embraced C# for that sort of thing, I’d probably have turned to D years ago. Between C# and Rust, I rarely find myself needing other tools aside from Makefiles and shell scripts.