Consensus Reached on Closure Proposals
Gafter writes that he has stopped his work on a prototype of closures to work on this JSR. He hopes for some good discussion at JavaOne about next steps, and re-iterates that the spec is a work in progress:
The purpose of the JSR proposal is to define the problems to be solved and circumscribe the permitted solution space. It doesn't mandate a particular solution, though it does offer the Closures for Java specification as an example of a solution to many (but not all) of the problems. This should not be surprising, as that spec was written specifically in an attempt to satisfy the requirements. Still, the spec is a work in progress.
The Editor's blog at Java.net points out that while this conensus moves us closer to having closures in Java, agreement on if we need or want closures is still up in the air.
So, according to Gafter, an agreement has been reached on what the problem is and what a closures JSR will try to address. The next question for the group to consider will be the specific form of their proposal. Assuming that is resolved and then brought to the community in the form of a draft JSR, it will be up to the JCP Executive Committee (and, really, to the community as a whole) to answer the first question: do we really even want this at all?
While this approach might seem to be out of order, the editor posits that it might be in order of difficulty.
Jon Whittle, John Hutchinson, Mark Rouncefield Oct 19, 2014
Shane Hastie Oct 17, 2014
Phil Brock & Rebecca Parsons Oct 16, 2014