using xvalue as lvalue about type_safe HOT 3 CLOSED

Could you provide a minimal example that reproduces the error?

from type_safe.

Your use of std::move is correct here (contrary to my first supposition).
The problem is actually purely conceptual and ocurrs when writing any assignment-like statements with rvalues on the lhs:

MyTypedef a = MyTypedef{1};
std::move(a) += MyTypedef{2};

/* or */
MyTypedef{1} += MyTypedef{2};

As rvalue assignment should be an error anyway, your implementation can be considered correct. Nevertheless I find the instanciation of this part of the macro to be conceptually incorrect as the resulting operators may never be used. Maybe I'm missing something but I think these two operators can be removed entirely.

from type_safe.

I was thinking about operator+= being marked with && (as in: rvalue ref qualifier). Not sure whether that's a thing.

from type_safe.