Hi Joe and Stuart,
Given the inconsistencies mentioned, I see how this change may not be worth the
hassle, so I’ll drop it. I appreciate the thoughtful responses to explain your
reasoning.
Thanks!
Ryan
> On Jul 7, 2023, at 4:21 PM, Stuart Marks wrote:
>
> Hi Ryan,
>
> Thanks for trying
Hi Ryan,
Thanks for trying out JDK 21 early access.
The issue you raise is indeed an inconsistency, but it's not clear which way it
should be resolved, or even whether it needs to be resolved, as the consequences are
quite minor.
Specifically, when the Sequenced Collections JEP was integrate
Thanks for laying out your thinking, Joe. I will watch your talks.
If I understood your response correctly, you are ok making such a change,
especially since it is semantically equivalent? If that’s the case, is JDK 21
past the point of feature release, or should the change target only 22? It
Hi Ryan,
Apropos of this discussion, I happened to recently give a talk to the
JCP that in part covered behavioral compatibility in the JDK:
https://jcp.org/aboutJava/communityprocess/ec-public/materials/2023-06-13/JCP-EC-Public-Agenda-June-2023.html
https://jcp.org/aboutJava/communityprocess/
Thanks for replying, Joe. First, let me reiterate, we fully admit
there was a bug in painless, we stopped short in walking the class
hierarchy. There is no bug in the SequencedCollection hierarchy. But I
do think there is an inconsistency.
> The two definition are semantically equivalent
> ...
> T
Hello,
What is Painless doing that would fail under
List extends SequencedCollection ...
but work under
List extends SequencedCollection, Collection ...
The two definition are semantically equivalent since SequencedCollection
itself extends Collection.
The JDK 22 javadoc for List s
Hi core-libs-dev,
I know various threads have existed over the past few months on
SequencedCollection and its implications on compatibility. I wanted to
raise this semi-related issue we noticed recently after beginning
testing against Java 21.
Elasticsearch began testing against Java 21, and noti