-
Bug
-
Resolution: Withdrawn
-
P4
-
17-pool, 21
Some java/security classes apply the below coding style,
Set<T> set = ...;
Set<T> unmodifiableSet = Collections.unmodifiableSet(new HashSet<>(set));
It may be unnecessary to wrap that set with HashSet before creating unmodifiableSet.
Some usages on Collections.unmodifiableList and Collections.unmodifiableMap have the same issue.
Set<T> set = ...;
Set<T> unmodifiableSet = Collections.unmodifiableSet(new HashSet<>(set));
It may be unnecessary to wrap that set with HashSet before creating unmodifiableSet.
Some usages on Collections.unmodifiableList and Collections.unmodifiableMap have the same issue.
- relates to
-
-
- Closed
-
-
JDK-6323374 (coll) Optimize Collections.unmodifiable* and synchronized*
-
- Resolved
-
- links to
-
Review
openjdk/jdk/15008