Bug 4360 - Wrong type for implicit array
Summary: Wrong type for implicit array
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Linux
: Lowest normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-04-10 07:00 UTC by Marek Safar
Modified: 2015-05-18 00:52 UTC (History)
2 users (show)

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

VS2011 (109.30 KB, image/png)
2012-04-11 12:11 UTC, Mike Krüger

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 Developer Community or GitHub 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 Marek Safar 2012-04-10 07:00:34 UTC
public class Test
	static int Main ()
		var v = new [] { null, 4 }; // Hover over var, MD shows int which is wrong
		return 0;

Another test case is

var v = new [] { "4", 4 };

which shows ?[]
Comment 1 Mike Krüger 2012-04-11 09:13:36 UTC
Both are error cases - atm our tooltips are not suited for showing resolve error cases. 

I think I've to improve the resolve results a bit for that as well.
Comment 2 Mike Krüger 2012-04-11 12:11:37 UTC
Created attachment 1654 [details]
Comment 3 Mike Krüger 2015-05-18 00:52:19 UTC
The roslyn resolver does the same.
But roslyn shows these errors in the editor on the fly therefore that's not an issue anymore.