On Sat, 26 Oct 2024 14:06:37 GMT, Naman Nigam wrote:
> As the documentation of getCeilingEntry currently reads, the inference is
> misleading as follows:
>
> if no such entry exists, returns the entry for the least key greater than the
> specified key;
> if no such entry
e
> specified key), returns {@code null}
> Have modified the first section to ensure that its clear that the value
> returned is upon existence of the key. Added a similar change for
> getFloorEntry.
Naman Nigam has updated the pull request incrementally with one additional
commit s
On Thu, 14 Nov 2024 02:36:38 GMT, Archie Cobbs wrote:
>> Naman Nigam has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> JDK-8343125 : Resolve a bad merge
>
> src/java.base/share/classes/java/util/Tr
On Wed, 13 Nov 2024 17:38:58 GMT, Chen Liang wrote:
>> Naman Nigam has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> JDK-8343125 : Resolve a bad merge
>
> src/java.base/share/classes/java/util/Tr
e
> specified key), returns {@code null}
> Have modified the first section to ensure that its clear that the value
> returned is upon existence of the key. Added a similar change for
> getFloorEntry.
Naman Nigam has updated the pull request incrementally with one additional
commit s
As the documentation of getCeilingEntry currently reads, the inference is
misleading as follows:
if no such entry exists, returns the entry for the least key greater than the
specified key;
if no such entry exists (i.e., the greatest key in the Tree is less than the
specified key), returns {@co
On Sun, 27 Oct 2024 02:30:33 GMT, Chen Liang wrote:
> To get a JBS issue, please open a bug report about this typo in
> https://bugs.java.com/bugdatabase/. Also follow https://openjdk.org/guide for
> the rest of the steps for contributions.
Thank you for your response @liach, I have
- [x] file
