Ambiguous method call with Action parameter overload

Question

I encountered some unexpected compiler behaviour when calling overloaded method with different Action variations.

Let\'s say I have this class

Answer 1

This is due to an implicit casting between long and decimal.

Here's a table of implicit castings(for simple types) in C#(Picture Source):

Read more about type conversions here.

Answer 2

When you pass TestDecimal or TestLong as a parameter you're in fact passing a method group (after all, there could be more than one TestDecimal method - it could have been overloaded). So in both cases implicit conversion occurs - from a method group to a particular delegate type. Both methods are thus applicable candidates (Section 7.4.2). From applicable candidates the overload resolution algorithm tries to find the best candidate. However, the rules of comparing conversions when matching parameter lists state, that if for both candidates implicit conversion occurs neither of them is better:

Section 7.4.2.3:

[...]

Otherwise, neither conversion is better.

That's why in your case there is an ambiguity.

---

The workaround is of course to first cast the parameter explicitly:

new Test(new Action<decimal>(TestDecimal))

This way for one case there will be no need for implicit conversion during overload resolution (as after the cast Action<T> type will match exactly), and the other would have to be converted (Action<long> to Action<decimal>), and the section mentioned above states that:

[...]

If S is T1, C1 is the better conversion.

If S is T2, C2 is the better conversion.

[...]

Answer 3

There is a workaround:

    Test t = new Test(new Action<decimal>(TestDecimal));