On Sat, 14 Jan 2023 03:56:33 GMT, Stuart Marks wrote:
>> Also additional verbiage regarding Map.Entry objects in general and their
>> possible connection to an underlying Map.
>
> Stuart Marks has updated the pull request incrementally with one additional
> commit since the last revision:
>
>
> Also additional verbiage regarding Map.Entry objects in general and their
> possible connection to an underlying Map.
Stuart Marks has updated the pull request incrementally with one additional
commit since the last revision:
Updates from Alan.
-
Changes:
- all: https://git.
On Fri, 13 Jan 2023 15:04:21 GMT, Alan Bateman wrote:
>> Also additional verbiage regarding Map.Entry objects in general and their
>> possible connection to an underlying Map.
>
> src/java.base/share/classes/java/util/Map.java line 421:
>
>> 419: * {@link Set#toArray toArray} overloads,
>>
On Fri, 13 Jan 2023 15:02:00 GMT, Alan Bateman wrote:
>> Also additional verbiage regarding Map.Entry objects in general and their
>> possible connection to an underlying Map.
>
> src/java.base/share/classes/java/util/Map.java line 405:
>
>> 403: * {@link Iterator} or implicitly via the en
On Thu, 12 Jan 2023 01:50:51 GMT, Stuart Marks wrote:
> Also additional verbiage regarding Map.Entry objects in general and their
> possible connection to an underlying Map.
src/java.base/share/classes/java/util/Map.java line 405:
> 403: * {@link Iterator} or implicitly via the enhanced {
Also additional verbiage regarding Map.Entry objects in general and their
possible connection to an underlying Map.
-
Commit messages:
- 8038146: Clarify NavigableMap/TreeMap support for Entry.setValue
Changes: https://git.openjdk.org/jdk/pull/11956/files
Webrev: https://webrevs.o