On Jan 10, 2014, at 2:42 PM, Paul Sandoz paul.san...@oracle.com wrote:
I have also removed the inconsistently applied synchronized block. Either we
apply it consistently to reporting or not at all. It was originally there
because we were not sure that the happens-before relationship [1]
Very helpful. Thank you for adding the comments.
Mike
On Jan 16 2014, at 03:26 , Paul Sandoz paul.san...@oracle.com wrote:
On Jan 10, 2014, at 2:42 PM, Paul Sandoz paul.san...@oracle.com wrote:
I have also removed the inconsistently applied synchronized block. Either we
apply it
Hi,
Some tweaks to the Stream forEachOrdered operation:
http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8029452-ForEachOrdered/webrev/
The first tweak is to size the CHM used in ForEachOrderedTask, this avoids
concurrent resizes and the costs associated with those.
The second tweak is to
On Jan 10 2014, at 05:42 , Paul Sandoz paul.san...@oracle.com wrote:
Hi,
Some tweaks to the Stream forEachOrdered operation:
http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8029452-ForEachOrdered/webrev/
The first tweak is to size the CHM used in ForEachOrderedTask, this avoids
On Jan 10, 2014, at 7:11 PM, Mike Duigou mike.dui...@oracle.com wrote:
The second tweak is to consolidate the reporting of elements to within the
ForEachOrderedTask.tryComplete method.
I have also removed the inconsistently applied synchronized block. Either we
apply it consistently to
