add move constructor documentation #4154
Conversation
WalterBright
requested review from
andralex,
maxhaton and
mdparker
as code owners
|
Thanks for your pull request, @WalterBright! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. |
| constructors make a copy of the original, while move constructors move the contents of | ||
| the original, and the lifetime of the original ends.) | ||
|
|
||
| $(NOTE Do not use postblits in the same struct with move constructors.) |
There was a problem hiding this comment.
If we have to have a warning like this, we should probably not support it.
There was a problem hiding this comment.
I plan on investigating if postblits should be allowed if there are move constructors.
There was a problem hiding this comment.
What I'm wondering here is perhaps we have been thinking about postblit a bit wrong.
Instead of it being the third hook, make it the common denominator of both copy/move constructors. So it is always called after they are.
There was a problem hiding this comment.
The rationale behind postblit was as another way to do a move constructor, not an enhancement to move constructors.
WalterBright
force-pushed
the
moveConstructor
branch
3 times, most recently
from
4765742 to
ca1fb56
Compare
WalterBright
force-pushed
the
moveConstructor
branch
2 times, most recently
from
621381d to
5ac133d
Compare
WalterBright
force-pushed
the
moveConstructor
branch
from
5ac133d to
6896d09
Compare
|
ready to pull |
As promised.