On Saturday, 26 June 2021 at 07:00:37 UTC, Ola Fosheim Grøstad
wrote:
Weak pointers aren't in the language, so I don't see why they
would matter here. I thought you were after replacing
GC-allocated class instances by a simple RC scheme.
One goal could be to make a class compatible with C++
On Saturday, 26 June 2021 at 04:24:05 UTC, frame wrote:
If you pass each file to the compiler like in your script then
every naming convention becomes irrelevant because the compiler
does not need to do a file system lookup anyway and a module
"foo_bar" could be also in the file xyz.d.
You
On Saturday, 26 June 2021 at 07:39:44 UTC, kinke wrote:
I'm pretty sure I haven't seen a weak pointer in C++ yet. I
don't look at C++ much anymore, but I suspect they are even a
lot rarer than shared_ptr.
Weak pointers are usually not needed, but sometimes you do need
them and then not
On Friday, 25 June 2021 at 23:55:40 UTC, kinke wrote:
I cannot imagine how weak pointers would work without an ugly
extra indirection layer. If we're on the same page, we're
talking about embedding the reference counter *directly* in the
class instance, and the class ref still pointing
On Saturday, 26 June 2021 at 13:49:25 UTC, Ola Fosheim Grøstad
wrote:
Is it possible to inherit from a C++ class and get a D
subclass, and is it possible to inherit from a D class and get
a C++ class?
Sure thing, with `extern(C++) class` of course.
But the best solution is to get to a place
On Saturday, 26 June 2021 at 20:03:01 UTC, kinke wrote:
With C++, you can today, an `extern(C++) class C` is equivalent
to and mangled as C++ `C*`. You can't pass it directly to some
`unique_ptr` or `shared_ptr` of course; an according D
wrapper reflecting the C++ implementation
