change which to return rather than show

[WestleyArgentum]

This is in response to discussion in #5566. I would be happy with either being merged :)

[StefanKarpinski]

Yes, this is much better.

[JeffBezanson]

It looks to me like whicht should throw the exception, then let which inherit that behavior.

[WestleyArgentum]

I thought so too, but I don't see a nice way to generate a MethodError with just arg types (and I don't know of a more appropriate error).

[WestleyArgentum]

Maybe whicht throws an ArgumentError, then which catches it and throws a MethodError?

[JeffBezanson]

Hmm that is a good point.

[JeffBezanson]

I think the answer is that whicht is redundant with methods and is not needed anyway.

[StefanKarpinski]

I agree that whicht should go away. I'd also like to see all the function that take a generic function and a signature rationalized to have similar signatures. As it is, some of them take a tuple of argument types, some of them are varargs and take the types as arguments and some of them take a tuple of argument values while others take a tuple of argument values. In other words, it's an inconsistent shitshow.

[JeffBezanson]

Examples? The only cases I'm aware of are which, which takes argument values as varargs, and every other function takes a tuple of types.

[JeffBezanson]

This convention (if it's worthy of that term) is also used by method_exists (type tuple) and applicable (varargs values).

[StefanKarpinski]

Perhaps I was overestimating the variety. If we're close to having consistent interfaces, that's great.