0
kicks
Generic Method Overloading Selection Pitfall
Recently I ran into a very unexpected behavior when working with an overloaded generic method. Basically, the selection process for overloaded versions of generic methods is different than their non-generic counterparts. Please be aware of this issue!