Lukas Eder

Thanks for the feedback, @amaembo. Within jOOλ, that's certainly true, but people might use the collectors exposed in [`Agg`](http://www.jooq.org/products/jOO%CE%BB/javadoc/latest/org/jooq/lambda/Agg.html) also for parallel JDK streams, or for StreamEx...

You're right. I'll think about a reasonable solution to this...

I can definitely see the problem, and the solution looks clever, but also a bit surprising. I'm not that much of a fan of the `return` variant. It also only...

There are essentially two options to solving this: 1. Adapt the existing method (incompatibly) 2. Introduce a new method for this purpose I'm currently favouring the latter, if we can...

Hah, nice ones :). Let's look at it more thoroughly. 1. The method will throw the argument exception. So, terms like "return" won't do the trick. 2. The return value...

While I totally agree with the criticism implied in the last name, none of these method names suggesed by @billoneil convey the fact that the method actually *throws* the argument...

> personally I think the method should be given a concise, simple name that hints at throwing and fake returning, and if someone actually wants to use it they'll read...

> It can't ever be executed because an exception will be thrown first... Yes, that's what I said :)

Noh, sorry, that's not going to do it. We're not in a hurry to add something like this to the library...

@asm0dey Sure, maybe. But that name still leads to the same confusion about the ambiguity introduced by a method that throws and returns at the same time.