Description
An enum based split would be useful.
Something like:
<E> List<TStream<T>> split(Class<E> enumClass, Function<T,E> splitter)
So the stream is split by the enum value with the returned streams in ordinal order.
This may have the benefit of being self-maintaining, so that if an enum value is added, the returned number of streams changes automatically, but only if given an enum class one can figure out the number of enums.
Based upon looking at the sample code in QUARKS-16
Attachments
Attachments
Issue Links
- relates to
-
EDGENT-47 Remove unnecessary null check in ConnectorStream.split(enumClass, splitter)
- Closed