Bug 15098 – C++ namespace conflicts with D import

Getting this error a lot: Error: namespace ud.kernel.kernel.ud conflicts with import ud.kernel.kernel.ud at udKernel\src\ud\kernel\kernel.d(3) This code: module ud.kernel.kernel; import ud.kernel.component; extern(C++, ud): class Kernel { ... } It seems the problem is that the root of the D namespace is 'ud', but my C++ namespace is also 'ud', and this doesn't seem to be acceptable. If I remove `ud.` from the D namespace, the errors stop. I think this is valid code, there are no guarantees that my C++ namespace is not the same as the root D namespace, infact it seems highly likely to me.

I guess one can argue that there is no need to name the D package exactly after the C++ namespace. Maybe by convention a '_cpp' could always be appended or you could change the D package name to 'unlimited_detail', because two letter variable names are shunned upon anyways. Let's see what the compiler devs say why it is this way.

Looks like this compiles: --- module ud.kernel.kernel; extern(C++, ud): class Kernel { } --- Is the problem in the import?

I guess the import introduces 'ud' in the local namespace, and the extern(C++) also introduces some 'ud' item into the local namespace... I'm not sure what kind of thing that 'ud' actually is. Marco: a long name at the root of the module hierarchy is really uncool, I would stick with 3 letters max. But I really would want it to be the same as the C++ if possible, since it's like, the same thing; a direct binding to the C++ code, so surely ALL the names should match, not just 'most' names.

The C++ binding depends on D code? Can C++ binding be moved it into a separate file so that it doesn't depend on D code and hence doesn't import D modules?

*** This issue has been marked as a duplicate of issue 13183 ***