let's play TDD, tackles closures in java
reinier at zwitserloot.com
Tue Dec 21 01:24:03 PST 2010
I do not agree with your assessment that its equally like to mix up
incrementAndGet(inc) vs. set(get() + inc), and foo += 20; and foo = 20. In
fact, += is currently defined as no different from foo = foo + 20, but if we
apply this to AtomicInteger, then all of a sudden there _is_ a difference -
a very important one, even.
I also do not agree that there's precedent with IINC vs. IADD. When you mix
up set(get() + 20) and incrementAndGet, you'll get thread sync bugs. These
are notoriously hard to debug and notoriously easy to miss. Mixing up IINC
vs. IADD doesn't lead to problems even remotely close to this.
Given that the current lambda sentiment is all about: "Let's be careful
handing folks dangerous weapons at this point in time - multicore is easy to
get wrong and there's not much experience around right now" - a sentiment I
happen to agree with, I rather doubt giving someone the tools to effectively
blow their leg off this easily and invisibly (foo = foo + 20; is a bug in
most scenarios, if foo is an AtomicInteger), well, it'll never fly. I don't
see any further point in discussing it, though we should revisit this issue
for coinflip, maybe there are ways to fix this*.
On Tue, Dec 21, 2010 at 10:07 AM, Artur Biesiadowski <abies at adres.pl> wrote:
> On 21/12/2010 08:41, Reinier Zwitserloot wrote:
>> AtomicInteger foo = 10;
>> foo = foo + 20;
>> would be desugared into either:
>> AtomicInteger foo = new AtomicInteger(10);
>> foo.set(foo.get() + 20);
> But you can write same thing with atomic integers right now ? Same way as
> you need to know difference between foo.set(foo.get() +20) versus
> foo.incrementAndGet(20), you would need to know difference between foo =
> foo+20 versus foo +=20 (and bytecodes iload, iadd, istore versus iinc)
> If you are concerned about what 'normal people' would do, normal people
> will write right now
> int holder = new int;
> holder += 20;
> and be completely sure it is atomic and threadsafe...
> But I agree that java is probably not ready for operator overloading yet.
> Same way as we constantly need to educate people that
> String str = "...";
> str += a;
> str += b;
> str += c;
> is something very different from
> str += a + b + c;
> there would be no end to suprises about 'non-intuitive' behaviour of
> Atomic* overloads.
> Artur Biesiadowski
More information about the lambda-dev