> See the bug description for details.
>
> I propose a simple solution. Let's allow ArraySpliterator to be non-SIZED and
> report artificial estimatedSize(), much bigger than the real one. This will
> allow AbstractSpliterator and IteratorSpliterator to produce prefix whose
> size is comparable
On Fri, 28 Jan 2022 15:37:59 GMT, Aleksey Shipilev wrote:
> Recent test regression after adding new cases in the test. Without compressed
> oops, ~1G elements `Object[]` array takes >8G of memory, which fails the
> test. The fix cuts it down to 512M when reference size is 8 bytes.
> Additional
On Fri, 28 Jan 2022 17:50:19 GMT, Mandy Chung wrote:
> `AccessibleObject::setAccessible` and `trySetAccessible` methods should only
> allow access to public member of a public type that is unconditionally
> exported consistent with the access check as described in the class
> specification, wh
Are you proposing dropping SIZED from the spliterator for arrays? This
would undermine all the array-based optimizations (e.g., toArray), which
seems a bad trade. I realize the splitting heuristics are frustrating
for a number of use cases, but this seems like throwing the baby out
with the b
On Fri, 28 Jan 2022 17:50:19 GMT, Mandy Chung wrote:
> `AccessibleObject::setAccessible` and `trySetAccessible` methods should only
> allow access to public member of a public type that is unconditionally
> exported consistent with the access check as described in the class
> specification, wh
On Fri, 28 Jan 2022 17:50:19 GMT, Mandy Chung wrote:
> `AccessibleObject::setAccessible` and `trySetAccessible` methods should only
> allow access to public member of a public type that is unconditionally
> exported consistent with the access check as described in the class
> specification, wh
Hello, Brian!
On Mon, Jan 31, 2022 at 12:01 AM Brian Goetz wrote:
>
> Are you proposing dropping SIZED from the spliterator for arrays? This would
> undermine all the array-based optimizations (e.g., toArray), which seems a
> bad trade. I realize the splitting heuristics are frustrating for a
On Sun, 30 Jan 2022 22:06:20 GMT, David Holmes wrote:
> There is no spec change here as you note, but the behavioural change also
> makes this warrant a CSR request IMO.
It's in draft: https://bugs.openjdk.java.net/browse/JDK-8280831, I assume Mandy
will finalize shortly.
-
PR: h
On Fri, 28 Jan 2022 17:50:19 GMT, Mandy Chung wrote:
> `AccessibleObject::setAccessible` and `trySetAccessible` methods should only
> allow access to public member of a public type that is unconditionally
> exported consistent with the access check as described in the class
> specification, wh
