RFR: 8341782: Allow lambda capture of basic for() loop variables as with enhanced for()

[Archie Cobbs]

On Thu, 10 Oct 2024 17:24:43 GMT, Maurizio Cimadamore <mcimadamore at openjdk.org> wrote:

> Having special rules for loop variables is sending us down the slippery slope of finding the next stable point between (1) and (2) - assuming one exists. The risk here is that once we start relaxing things in some areas (e.g. loops) you can quickly run into issues where other deficiencies in capture become even more apparent.

I agree with all of that as well. There is one valid counter-argument though (reflected in the JEP draft) which is that we have already taken this current step with enhanced `for()` loops, so we're not really establishing any much of a new "frontier" with this feature by adding the same thing to basic `for()`. In other words, enhanced `for()` is an intermediate design point that's already been taken, for better or worse, so we might as well make the most of it. Or put more plaintively, "Please don't blame this feature for all the world's problems" :)

Regarding the bigger picture question, I'm skeptical that there exists any other design point between 1 and 2 that would be preferable to just jumping straight to 2, i.e., capture anything that's DA anywhere, but of course anything's possible.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/21415#discussion_r1795868774