Re: [boost] [shared_ptr] dangerous implementation of moveconstructor

From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2007-04-17 14:47:08

> If we left that undefined the complexity of a move operation could be
> terribly varying depending on the implementation, and by consequence,
> unusable. In a container, for example, operation complexity refers to
> search and copy, but in node containers destroying values is orders of
> magnitude slower than doing a search. Information is power.

Information is power, but limiting the specification of an interface often 
makes better, more optimal implementations possible.