On Tue, Oct 2, 2018 at 2:40 AM Walter Bright via Digitalmars-d <digitalmars-d@puremagic.com> wrote: > > On 10/2/2018 2:17 AM, Walter Bright wrote: > > 1. Don't allow moving of C++ structs > > 2. Add a struct attribute that means "not moveable" > > 3. DIP 1014, which is add a __move_post_blit() function (most complex > > solution) > > 4. Use copy/destruct for C++ structs that have copy constructors (this is > > the > > old C++ solution, and is less efficient than the move constructor) > > The postblit solution can also work today, > > https://issues.dlang.org/show_bug.cgi?id=17448#c37 > > as the DMD compiler doesn't actually move structs.
Sorry... what?! DMD doesn't move? O_O We've been talking endlessly about move semantics for like, 10 years... Do the other compilers move? I don't understand... I've missed something. > So you're OK for the time > being until DMD does, or a copying garbage collector is implemented. Ummm...