RFR(m): 8159404: immutable collections should throw UOE unconditionally
martinrb at google.com
Fri Sep 2 03:41:48 UTC 2016
Looks good to me!
Another idea for another day: I would like the immutable collections to be
more optimal than they currently are, even if we have to write more code.
It bugs me is that all of these collections have a modCount, despite never
being modified! (Even for mutable lists, I'm not sure the added safety of
modCount was worth the price)
java -jar jol-cli-0.5-full.jar internals
java.util.ImmutableCollections$List1 object internals:
0 12 (object header) N/A
12 4 int AbstractList.modCount N/A
16 4 Object List1.e0 N/A
On Thu, Sep 1, 2016 at 6:47 PM, Stuart Marks <stuart.marks at oracle.com>
> Hi all,
> Please review this change to make the immutable collections (List.of,
> Set.of, Map.of) throw UnsupportedOperationException unconditionally. That
> is, they should throw UOE even if a mutator method is called with arguments
> that make it a no-op. Calling a mutator method on an immutable collection
> is always a programming error, and having it sometimes be a no-op
> potentially leads to errors.
> Note that the existing Collections unmodifiable wrappers always throw UOE
> unconditionally. This change makes the immutable collections behave
> consistently with the unmodifiable wrappers. For example,
> List<String> unmodList = Collections.unmodifiableList(new
> unmodList.addAll(List.of()); // throws UOE
> List.of().addAll(List.of()); // currently does nothing, change to
> throw UOE
> Unfortunately, various other specialized collections such as emptyList()
> etc. behave differently, e.g.
> Collections.emptyList().addAll(List.of()); // does nothing
> However, that change will be left for another day.
More information about the core-libs-dev