30 Nov
2008
30 Nov
'08
12:11 p.m.
Ion Gaztañaga wrote:
Because in the review the two step construction (default ctor + open()) was considered harmful. I guess now it would be useful in the presence of move semantics.
If you implement move as swap, there is no problem at all. You could still implement move as transfer, leaving the moved-from object in some state where only destruction and assignment are valid; there is no need to make that state reachable from public default-construction.