9cecd69a9e
This check is obsolete but leads to problems. It appears when resolving recursive calls (see sameTypeParameterUse.kt): `foo<R>(x: R, y: R)` within call `foo<R>(x, "")` after substitution has R as type of it's second argument, and when checking value arguments, x is not checked because supposed to be dependent on type parameter of candidate (that is effectively false), so there are two successful candidates in resolution results and wrong OVERLOAD_RESOLUTION_AMBIGUITY error.