You must not use :_* here.
There reason why _* exists is that varargs may lead to ambiguities.
In java If you have f(int... values) you may call f(1, 2, 3), but also have do
int[] values = {1, 2, 3};
f(values)
With ints, it is ok. But if you have f(object.. values) and have object[] values = {"a", "b"}, when calling f(values), should it means that f is called with a single arg, which is the values, or with multiple args "a" and "b"? (java chooses the later).
To avoid that, in scala, when there are varargs, it is not allowed to pass them as arrays (actually the more general Seq in scala) argument, except if you explicitly says you are doing so, by putting the abscription :_*. With the previous example, f(values) means values is the single argument. f(values: _*) means each element of values, whether there are zero, one, or many, is an argument.
In your particular case, you are passing the Predicate arguments (actually just one) as separate (well...) predicates, not as a collection of predicates. So no :_*
Edit: I read the post you linked to more carefully. While what I certainly believe what I have written above is true, it is probably not helpful. The proper answer was given by MxFr:
- Since scala 2.9, interaction with java varargs is ok. just pass condition
- Before that, you must pass your arguments as an array, and put :_*