On Friday, 29 June 2018 at 07:37:46 UTC, FeepingCreature wrote:
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
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
On Friday, 29 June 2018 at 07:15:38 UTC, FeepingCreature wrote:
I'm doing a pull request to rewrite Nullable to use
moveEmplace/move to replace its internal value. I'm considering
whether it's better to let Nullable destroy its existing value,
then memcpy the new one over it (via move()), or
I'm doing a pull request to rewrite Nullable to use
moveEmplace/move to replace its internal value. I'm considering
whether it's better to let Nullable destroy its existing value,
then memcpy the new one over it (via move()), or if it already
has a value in it, if an opAssign to Nullable
