Decommission Enum.values() and replace it with Enum.entries

[qwwdfsad]

No description provided.

[CLOVIS-AI]

What are the benefits of EnumEntries<E> being a List<E> instead of a Set<E>? As an immutable set, it could reuse the same strategies as Java's EnumMap for a fast contains() implementation.

[gildor]

@CLOVIS-AI Set is an unordered collection, but the order is very important for Enum values in many cases, also you cannot access values by index (ordinal) in set, which is one more important case for collection of enum values

[elizarov]

@CLOVIS-AI What are the benefits of EnumEntries<E> being a List<E> instead of a Set<E>? As an immutable set, it could reuse the same strategies as Java's EnumMap for a fast contains() implementation.

To add to the answer by @gildor, having EnumEntries<E> as List<E> does not prevent us from reusing the strategy for a fast contains() implementation, but it also makes possible for a fast retrieval of an entry by its ordinal (index) using get(Int) method which a Set does not have.

[ilya-g]

Overall good text.
Also, since it proposes to introduce new API in a new package, it may make sense to explain that choice: why new package, and why it is named like that.