capturing (or not) mutable local variables

[Neal Gafter]

On Monday, November 22, 2010, Brian Goetz <brian.goetz at oracle.com> wrote:
> In any case, I think it is time to close this discussion.  You've made your
> point, some people agree with you, and some others disagree.  But we do not
> intend to lift this restriction at this time, and I don't think further
> discussion will bring to light any issues that have not already been
> considered.  We can always revisit this issue in a future iteration (choosing
> not to lift a restriction now does not foreclose on our ability to do so later).

There is a way to satisfy both parties.  Have the specification
mandate a warning, and provide a way for the programmer to suppress
the warning, effectively saying "I know what I'm doing.".  (a way to
escalate it to an error is good too)  That's the approach taken with
the latest revisions of BGGA and CfJ.