Seems to have happened right at the start of moving VirtualFlow into public scope (which included lots changes to the implementation plus some refactoring, codereader's brain cells need to be kept alert ;)

see my comment at https://bugs.openjdk.java.net/browse/JDK-8197536

Zitat von Nir Lisker <nlis...@gmail.com>:

I tested the issue. It is not present in 1.8.0_152-b16, but it is present
in 9+181 and 10-ea+37.

- Nir



Reply via email to