stealing inside the move constructor
- by FredOverflow
During the implementation of the move constructor of a toy class, I noticed a pattern:
array2D(array2D&& that)
{
data_ = that.data_;
that.data_ = 0;
height_ = that.height_;
that.height_ = 0;
width_ = that.width_;
that.width_ = 0;
size_ = that.size_;
that.size_ = 0;
}
The pattern obviously being:
member = that.member;
that.member = 0;
So I wrote a preprocessor macro to make stealing less verbose and error-prone:
#define STEAL(member) member = that.member; that.member = 0;
Now the implementation looks as following:
array2D(array2D&& that)
{
STEAL(data_);
STEAL(height_);
STEAL(width_);
STEAL(size_);
}
Are there any downsides to this? Is there a cleaner solution that does not require the preprocessor?