Effectively final effective?

[Peter Levart]

On Thursday 25 February 2010 17:44:44 Reinier Zwitserloot wrote:
> It's still more than a month until April 1st.

Sorry, It was another bad idea. I apologize.

Now, seriously:

> ....
> 
> NB2: Without an explicit 'safe / unsafe' closure concept, turning local
> variables into heap-allocated non-thread safe variables is a major change
> and something that you should always be careful with. *with* an explicit
> 'safe / unsafe' closures concept, the solution is of course to state that
> safe closures may mutate variables from their enclosing scope, and for the
You meant 'unsafe', didn't you?
> compiler to sort out how to make it happen. This idea is therefore either
> dangerous or unnecessary, depending on if safe/unsafe closures somehow make
> it into lambda-dev.
> 

Would a '@Safe' qualifier as a JSR 308 checker plug-in be enough to warn against 'unsafe' functions?

Peter