[_yosefk]

Most useful C++ code is either not templates or it's templates which can be instantiated a finite number of times and then used like non-templated code. Most "header-only"/header-heavy C++ libraries which present the problem you mention solve problems like C++'s smart for loop working like "for x in xs" does in Python but not working like "for x,y in zip(xs,ys)" does or like "for i,x for enumerate(xs)" does etc.; you don't really need these outside C++ (whether you need them inside C++ is another question but it's irrelevant here.)

[CJefferson]

That sounds ..wrong. what about the C++ standard library? Neither vector or sort sounds like that?

[yorwba]

Those > can be instantiated a finite number of times and then used like non-templated code.

So you have a C++ file that uses vector<int>, vector<struct c_struct>, vector<CppClass>, vector<DClass>, etc. once and then you can link to them from D code.

The only case where that doesn't work is when you have lots of one-off instantiations, where requiring an instantiation in C++ code for each use in D would get annoying quickly.

[amelius]

Does the D compiler know how to mangle/demangle C++ names?

Do you have to write some kind of D header file for foreign C++ functions? Otherwise, how would D even know about the existence of e.g. vector<int>::push?

[biotronic]

https://dlang.org/spec/cpp_interface.html#cpp-templates

You will need to recreate the C++ function definitions in D and mark them extern(C++), but that's about it.

[pzone]

Those parts of the C++ standard library are header-only and will be instantiated with concrete types at compile-time.