Bug 14053 - Property and Generic method generate weird ambiguity problems
Summary: Property and Generic method generate weird ambiguity problems
Status: RESOLVED FIXED
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2013-08-17 00:10 UTC by Jessy Catterwaul
Modified: 2013-08-17 05:15 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Jessy Catterwaul 2013-08-17 00:10:52 UTC
Description of Problem:


bool False<T>() 
{ 
	return false;
}

bool False
{ 
	get { return false; } 
}

bool b = False<bool>();
b = False; // generates a different error depending on whether the method or property comes first in the file.


Actual Results:
All code but the last line compiles.  Then, what the comment says.

Expected Results:
No errors, because there isn't actually any ambiguity.
Comment 1 Marek Safar 2013-08-17 05:15:35 UTC
Fixed in master.