Tasks.<T>par(emptyIterable<? extends Task<? extends T>>) should not throw IllegalArgumentException about parseq HOT 6 CLOSED

I agree this should have been the behavior from the very beginning but unfortunately such change is backwards incompatible and might break existing code.

from parseq.

@jodzga, do you mean there could be code that relies on Tasks.par() to throw an IllegalArgumentException in case an empty collection is passed as its argument?
Or on ultimate List<T> being non-empty?

from parseq.

I can imagine both.
Our current thinking is to create Task.par() with better semantics, deprecate Tasks.par() and point it to Task.par().

from parseq.

Yeah, that should work. Otherwise developers would have to introduce their own sets of utility classes. No big deal, but it's good to have one from the authors :)

from parseq.

I've submitted a PR for this issue last week, which should be merged sometime this week: #113

from parseq.

@jodzga Should be safe to close this issue now. :)

from parseq.