Hi, I was wondering if there are any plans (or any reasons against) adding these things to Seq or an extension of it:
1. Simpler stream collecting, such as items.stream().filter(...).map(...).toList() instead of having to use the more verbose .collect(Collectors.toList()) as a terminal call. Or even have mapToList(...) as a terminal call. 2. Avoiding the need to call .stream() so that collections and streams are the same thing (as in Scala IIRC). For example: for List<Item> items, calling items.mapToList(...) would produce a transformed list. (I thought of using bytecode manipulation to enhance the JDK classes on class-loading but it would have licensing issues. Therefore, this idea would require creating a new class hierarchy on a separate package outside java.* which perhaps a program could generate) Thanks -Raul -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
