Destructors, const structs, and opEquals

[so]

> If parameters are 'in' or 'const' by default, then whether they are  
> passed by value or by ref has no consequence, I guess. The compiler can  
> then safely choose the most efficent more --what it can do as it knows  
> sizeof-- grossly structs by ref, the rest by value. Is this reasoning  
> correct?

This kind of design decisions, leaving this responsibility to compiler is  
very wrong.
Also, you are introducing a lock in here, no way to do the opposite.
"T& a" "ref T a" are very good tools. You can't always assume compiler  
always knows the best.

"If parameters are in or const" what about if not? Another inconsistency  
and a quite a bad one at it.

-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/