Bug 2216 - 'new' context does not handle anonymous/implicit array declaration
Summary: 'new' context does not handle anonymous/implicit array declaration
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: master
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2011-11-28 06:54 UTC by Alan McGovern
Modified: 2015-08-20 03:24 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 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:
Status:
RESOLVED FIXED

Description Alan McGovern 2011-11-28 06:54:37 UTC
foreach (var v in new [] { "string" })

The above is a valid way of declaring a string array, however the autocomplete engine does not allow me to type brackets after typing 'new'. I end up getting this in my code:

new AccessViolationException[
Comment 1 Alan McGovern 2011-11-28 06:54:50 UTC
(new resolver branch)
Comment 2 Alan McGovern 2011-11-28 06:58:53 UTC
Also if i have this code:

new [] { Tuple.$ };

I do not get any completion for the tuple type once inside the array context.
Comment 3 Mike Krüger 2011-12-14 03:43:22 UTC
fixed.

btw. I would prefer having 1 report for 1 bug, we had it in the past that bugs got mixed up, and if there is just one out of n bugs that can't be fixed all bugs are 'open' forever :(.