JSR 335 seems outdated, not aligned with implementation

[Brian Goetz]

> Maybe my sentences were too strict. So I'll try to put this a bit
> differently: I'm ready to be an early adopter and spend time by
> following changes in specs. My question was more about how to be
> notified about such changes without digging too much into codebase of
> OpenJDK. E.g. when planned to update specs to reflect recent changes?

Then -- welcome!  We're happy to have tools like Sonar as early adopters!

So, here's a rough description of the current status.

- The EG has agreed on most of the major points for the language, 
especially as to how it affects syntax and parsing.  There are still 
fine points being resolved on the interaction of type inference and 
method overload selection, but this probably doesn't affect Sonar.  This 
is a good time to start thinking about tool support for new language 
features.

- The recent 0.6.0 specification mostly captures the language and VM 
decisions made so far.

- The implementation in the lambda repository is mostly, but not 
entirely, caught up with the 0.6.0 specification.

- The periodic binary drops on the Project Lambda OpenJDK page are often 
a few weeks behind the current lambda repository tip.

- The implementation in the JDK8 repository and drops lags the lambda 
repository further, but what is there is expected to be stable.