Here’s a pattern that I’ve seen occur a number of times - a pair of method overloads, one accepting
and the other accepting
params edition is provided as a convenience overload, making the API simpler for consumers. The
implementation is usually a simple delegation call to the main method:
There’s a trap here though - as shown, you’ll get a Stack Overflow exception thrown in good order.
The reason is simple - but perhaps not obvious. When the compiler is matching method signatures to work out which
Process() to invoke, there’s a better match with
string than with
IEnumerable<string>, so the
generated code goes into a tight loop.
The solution is to cast
parameters to the more general type so that there is only one viable match:
The way that the compiler selects which overload to call is entirely predictable, but complex, and sometimes gives unexpected results. It’s worth learning enough about the process to be able to troubleshoot problems (like this one). That said, if your specific problem is too complex, the best answer might be to rename some of the overloads so that a future maintainer doesn’t have the same problem to face.