Regular sync-ups from the upstream?
aleksey.shipilev at oracle.com
Mon Feb 18 00:48:56 PST 2013
It seems the lambda/lambda is the frontier of concurrency development
these days. Both Doug had locked jsr166 to be compilable with the latest
lambda/lambda, and me as well locked java-concurrency-torture to be
compilable with the latest promoted build of jdk8-ea-lambda. (These
address compilation of all these fancy lambda-enabled APIs).
With the headlines like that, I'm going to ask regular sync-ups with the
upstream to bring more goodness from regular channels, including
non-lambda-specific j.u.c.*/HotSpot changes. Many of j.u.c. changes are
pushed directly into jdk8.
Example: @Contended already accessible in jdk8-b75 (promoted Jan 31),
but not accessible in jdk8-lambda-b76 (promoted Feb 05?),
jdk8-lambda-b77 (promoted Feb 11?).
Maybe I'm missing some part of the plan to integrate lambda/lambda to
upstream jdk8 completely, which will move the development back to
mainline, and the whole issue would be nilled out.
More information about the lambda-dev