Yes, but like I've said to you before, they're problematic and find themselves interfering with the situation frequently.

It's possible to reconcile this, but I agree it would be better to move away... but that's very hard to do in practise.

postblit has innertia, and failure to implement copy/move constructors because of an interaction with postblit tends to lead to resolving the issue by writing another postblit... that doesn't lead us in the right direction.

On Sun, 27 Apr 2025 at 11:46, Walter Bright via Digitalmars-d <digitalmars-d@puremagic.com> wrote:

Postblits and rvalue references do not mix.

Move constructors and rvalue references are a replacement for postblits. We
didn't make any effort to reconcile the two.

If you're going to use move constructors and rvalue references, just delete the
postblit code from the struct hierarchy.

Postblits are now an obsolete feature, left for legacy code.