On Friday, 29 June 2018 at 07:31:42 UTC, Eugene Wissner wrote:
You can move only exactly the same type. with opAssign you can assign a differnt type. So opAssign should forward assignment to the underlying type if you assign nor Nullable!T nor T.

Sorry, that was unclear; I meant to ask for usecases for T::opAssign(T). Maybe the reason to allow this is just that it's a generalization of the actually useful T::opAssign(S), but I want to know if there's a specific usecase for calling specifically T::opAssign(T).

Reply via email to