Effectively final effective?

[Jesse Kuhnert]

If anonymous inner classes are something everyone thinks shouldn't be
there anyway then they shouldn't be considered too strictly. Shouldn't
they become obsolete with this project anyways?

The threading issues do sound like something worthwhile exploring very
thoroughly though,  given the predominent environment the language
runs in.  Tough choice there..

On Thursday, February 25, 2010, Paulo Levi <i30817 at gmail.com> wrote:
> Final should have been the default, non null should have been in the
> language (and default), constructors should have not been allowed to call
> protected methods, closures should have come on day one, reification should
> have been included in generics, i miss map and reduce on arrays & lists, i
> like list generators and RIIA and would love it in java.
>
> The discussion is if it is worthwhile to allow final by default for captured
> variables in lambdas considering that
> a) anonymous classes have the opposite behavior, so things get slightly
> inconsistent.
> b) it is safer for threaded use.
>
>