On Tue, 26 May 2026 19:17:44 GMT, Volker Simonis <[email protected]> wrote:
> I'm also not so much concerned about JDK 27, so although I disagree with this > PR, I don't think it will create a lot of harm because nobody will using it > in production anyway. We still have enough time to fix this until the next > LTS will be released, but I **strongly** advocate for a solution that can be > downported to JDK 17, 21 and 25 as well. Our focus has to be forward looking. If fixing the issue with streams that contain a series of members, in conjunction with an underlying stream that doesn't have a useful available() implementation, can't be fixed without behavioural compatibility issues then we have the option of deprecating the existing constructors, and adding a new constructor or factory method. The backports are unfortunate but should not be our focus right now. It might be that they need a system property or some knob to deal with the issue on JDK 25u at least. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30925#discussion_r3310172782
