RFR(m): 8177290 add copy factory methods for unmodifiable List, Set, Map
Roger.Riggs at Oracle.com
Wed Nov 1 20:50:28 UTC 2017
A few editorial comments:
Collection.java: Lines 110, 133, 166
The bold labels probably want to be on their own lines and not
terminated by "." to look like headings
(or be headings if the CSS supports them)
List.java: Consistency of markup references to unmodifiable List|Set|Map.
The List.of constructors put the reference on a separate line, but the
does not. You could probably omit the blank line.
(BTW, the copyOf constructor does not always create a copy; I'm not sure
if the method
name will result in an incorrect assumption but it may be misleading or
a spec issue.)
The same observations are true for Map and Set constructors.
On 10/31/2017 7:49 PM, Stuart Marks wrote:
> Updated webrev, based on comments from Brian and Roger:
> On 10/30/17 3:50 PM, Stuart Marks wrote:
>> (also includes 8184690: add Collectors for collecting into
>> unmodifiable List, Set, and Map)
>> Hi all,
>> Here's an updated webrev for this changeset; the previous review
>> thread is here:
>> This webrev includes the following:
>> * specification revisions to provide clearer definitions of "view"
>> collections, "unmodifiable" collections, and "unmodifiable views"
>> * new List.copyOf(), Set.copyOf(), and Map.copyOf() "copy factory"
>> * new Collectors.toUnmodifiableList, Set, and Map methods
>> * tests for the new API methods
>> I've added some assertions that require some independence between the
>> source collection (or map) and the result of the copyOf() method.
>> I've made a small but significant change to Set.copyOf compared to
>> the previous round. Previously, it specified that the first of any
>> equal elements was preserved. Now, it is explicitly unspecified which
>> of any equals elements is preserved. This is consistent with
>> Set.addAll, Collectors.toSet, and the newly added
>> Collectors.toUnmodifiableSet, none of which specify which of
>> duplicate elements is preserved.
>> (The outlier here is Stream.distinct, which specifies that the first
>> element of any duplicates is preserved, if the stream is ordered.)
>> I've also made some minor wording/editorial changes in response to
>> suggestions from David Holmes and Roger Riggs. I've kept the wording
>> changes that give emphasis to "unmodifiable" over "immutable." The
>> term "immutable" is inextricably intertwined with "persistent" when
>> it comes to data structures, and I believe we'll be explaining this
>> forever if Java's "immutable" means something different from
>> everybody else's.
>> add copy factory methods for unmodifiable List, Set, Map
>> add Collectors for collecting into unmodifiable List, Set,
>> and Map
More information about the core-libs-dev