Checked overload for std.algorithm.mutation.move.
TODO Can we somehow prevent users of Owned from accidentally using std.algorithm.mutation.move instead of this wrapper?
See Implementation
Checked overload for std.algorithm.mutation.move.
TODO Can we somehow prevent users of Owned from accidentally using std.algorithm.mutation.move instead of this wrapper?