dstep

ar with C/C++ D is closer to C/C++ than Zig IMO. One of it's design goals is actually: "10. Where D code looks the same as C code, have it either behave the same or issue an error." And: "The general look and feel of C/C++ is adopted. It uses the same algebraic syntax, most of the same expression and statement forms, and the general layout." See: https://dlang.org/overview.html#goals I found Zig to be much less syntactically similar to C/C++ than D. Zig felt more like a mix of Rust/Go. > the features it adds on top of C (e.g. slices, compile time execution) D also has slices and (outside of Lisp) was the first programming language I believe to introduce CTFE and CTFE-based metaprogramming. C++'s implementation as I understand it is essentially lifted from D. - https://dlang.org/articles/d-array-article.html#introducing-... - https://tour.dlang.org/tour/en/gems/compile-time-function-ev... > its translate-c utility works amazingly well at transpiling C code to Zig As stated above, not required due to ImportC, but there are several tools to automatically generate "extern" bindings to C/ObjectiveC/C++. You use these if you're linking with an external out-of-tree library, or a C++ library. - C, Limited C++ = https://dlang.org/blog/2019/04/08/project-highlight-dpp - C, Extensive C++ = https://github.com/Superbelko/ohmygentool - C, Objective-C = https://github.com/jacob-carlborg/dstep > its test blocks make unit testing trivial to integrate. Again, D also has this: - https://tour.dlang.org/tour/en/gems/unittesting ============= Not trying to start a pissing match, because I actually think that Zig has a lot to offer as well -- but for these particular list of things, there's no clear winner here.

you have "d++", which lets you "#include" C/C++ headers. Under the hood tries to run an automatic syntax conversion. It can't handle <std> but for simple code it works and can spit out the equivalent D. https://github.com/atilaneves/dpp Also you've got "dstep", which is "A tool for converting C and Objective-C headers to D modules" https://github.com/jacob-carlborg/dstep And finally you have the somewhat abandoned (but as far as I know mostly functional) Calypso, which is a fork of the LLVM-based D compiler that supports direct interop with C++. It's a pain to build though, haven't gotten around to trying to build it, but it does look wicked cool: https://github.com/Syniurge/Calypso pragma (cppmap, "cppheader.h"); // tells Clang to parse cppheader.h but do not import anything import (C++) NamespaceA.Class1; // imports NamespaceA::Class1 import (C++) NamespaceA; // imports the full namespace import (C++) *; // imports the entire translation unit So I am hopeful about the future of the relationship between C++ and D. I would really have loved to have not written that C++ lol.