3 ms·

Carbon's memory model is compatible with C++'s[1], so where would you foresee complications? D could have been so much better here if it just hadn't chosen to b

Carbon's memory model is compatible with C++'s[1], so where would you foresee complications? D could have been so much better here if it just hadn't chosen to be a GC'd language. That single choice pretty much kills any easy interop. 1: "For example, C++ and Carbon will use the same memory model." https://github.com/carbon-language/carbon-lang/tree/trunk/docs/design#bidirectional-interoperability-with-c-and-c https://github.com/carbon-language/carbon-lang/tree/trunk/do...

zozbot234 4y ago
AIUI, you don't need to use D with a garbage collector. It can be disabled.
- dymk 4y ago
  The D standard library is heavily tied to the GC. If you want to avoid the GC, you'd have to give up the standard library, and if you do that, you have to give up most of the D ecosystem. As far as I can tell, there hasn't been progress in untying the stdlib from the GC - https://github.com/dlang/projects/issues/56 https://github.com/dlang/projects/issues/56
  - deleted 4y ago
    [deleted]
  - int_19h 4y ago
    You don't need non-GC stdlib for C++ interop, though.