let's play TDD, tackles closures in java

[Peter Levart]

On 12/20/10, Reinier Zwitserloot wrote:
> Boxing
> for Atomics is a much bigger deal, though (as boxing for java.lang.Integer
> and friends has shown). There'd be far less complexity if this boxing only
> works for assignments / variable initializations.
> 
> i.e.:
> 
> AtomicInteger foo = 10; // this works

// and would, pressumably be translated to:
AtomicInteger foo = new AtomicInteger(10);

> foo = 20; // this works

// but is not known whether it should be translated to:
 foo = new AtomicInteger(10);
// or to:
foo.set(10);


Atomic* classes are mutable containers - not like immutable primitive wrappers that can, to some limited degree, mimic the value semantics.


Regards, Peter