Ruling out arbitrary cost copy construction?

[Pillsy]

Steven Schveighoffer Wrote:

> On Wed, 06 Oct 2010 12:34:54 -0400, Andrei Alexandrescu  
> <SeeWebsiteForEmail at erdani.org> wrote:
[...]
> > 2. It would force certain types (such as BigInt) that allocate
> > resources and have value semantics to resort to reference 
> > counting.

> Or to be considered immutable.  I believe Java does it this way.  Of  
> course, Java's GC is much better at dealing with this...

I would vote prettty strongly for immutability for things in the standard library. I think the abstraction isn't as leaky and designing library interfaces around current GC QoI issues strikes me as a bad plan.

Cheers,
Pillsy