Bug 28837 - Problems determining overloading candidate
Summary: Problems determining overloading candidate
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: 3.12.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2015-04-07 07:57 UTC by gaiseras
Modified: 2015-04-07 11:58 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description gaiseras 2015-04-07 07:57:05 UTC
The following source code

public class B

public class AClass
  public static int Foo(System.Type t, bool b = false, int x = 0)
        return 1;
  public static int Foo(System.Type t, params int[] x)
        return 2;
  public static int Foo(System.Type t, params B[] x)
        return 3;

  public static void Main()
    B b = new B();


produces ambiguity errors with mcs:
foo.cs(26,5): error CS0121: The call is ambiguous between the following methods or properties: `AClass.Foo(System.Type, params int[])' and `AClass.Foo(System.Type, params B[])'
foo.cs(13,21): (Location of the symbol related to previous error)
foo.cs(17,21): (Location of the symbol related to previous error)
Compilation failed: 1 error(s), 0 warnings

However, mono version 3.8 (and csc) seems to work fine with the code.
According to from the C# language spec (5.0), the first method should be chosen (I think),
because it can be applied in the call below in its normal form?
Comment 1 Marek Safar 2015-04-07 11:58:35 UTC
Fixed in master