12.6.4.1 & 12.7.6.2: Overloading resolution is too simple, so let's make it repeat steps...

From §13.6.4.1 (Overloading Resolution – General):

> - First, the set of candidate function members is reduced to those function members that are applicable with respect to the given argument list (§13.6.4.2).

From §13.7.6.2 (Method invocations):

> - The set of candidate methods for the method invocation is constructed. For each method `F` associated with the method group `M`:
> - If `F` is non-generic, `F` is a candidate when:
- `M` has no type argument list, and
- `F` is applicable with respect to `A` (§13.6.4.2).

So the candidates are reduced to those that are applicable, but a method is only a candidate if it is applicable...

This longstanding bit of fun came up as an issue when trying to improve the wording of the non-ambiguous ambiguity example covered by ECMA-TC49-TG2/spec#776.

We probably really need something like a clear progression "candidate -> applicable -> best", maybe in the "pre C# 6" phase?