Bug 5409 - Inconsistent behaviour of IComparer/BinarySearch in MONO compared with .NET
Summary: Inconsistent behaviour of IComparer/BinarySearch in MONO compared with .NET
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-05-30 05:57 UTC by m3nikma7i
Modified: 2012-06-01 03:23 UTC (History)
4 users (show)

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

Test case which demonstrates inconsistency between Mono and .NET (1.49 KB, text/plain)
2012-05-30 05:57 UTC, m3nikma7i

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 m3nikma7i 2012-05-30 05:57:13 UTC
Created attachment 1984 [details]
Test case which demonstrates inconsistency between Mono and .NET

The order of arguments in IComparer.Compare() in MONO is the inverse of the order of arguments in .NET. 

I have attached a test case which demonstrates the issue. It produces the correct result using Microsoft .NET, but an error using MONO.

Running the same test case code, the result on MS .NET is:

    Correct result (.NET): 1-3 is in range 0-9

whereas on MONO we have:

    ERROR (Mono): The given input was not found in any ranges!
Comment 1 m3nikma7i 2012-05-30 06:25:54 UTC
I forgot to say the obvious. I suspect this is a problem in BinarySearch() which passes the arguments in the wrong order.
Comment 2 Marek Safar 2012-05-30 09:33:12 UTC
Fixed in master
Comment 3 m3nikma7i 2012-05-30 10:03:43 UTC
Thanks! =)
Comment 4 Miguel de Icaza [MSFT] 2012-05-31 17:24:04 UTC
Do we need to put this on 2-10 and mobile-master?
Comment 5 Marek Safar 2012-06-01 03:23:44 UTC
No, it's a breaking change which may require user code changes