Bug 2788 - Locals do not show up inside the 'for' statement context
Summary: Locals do not show up inside the 'for' statement context
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: High normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-01-09 06:43 UTC by Alan McGovern
Modified: 2012-01-12 10:37 UTC (History)
1 user (show)

Tags: resolver
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:

Description Alan McGovern 2012-01-09 06:43:36 UTC

var foo = new byte[100];
for (int i = 0; i < fo$

MonoDevelop new resolver master does not offer 'foo' as a valid completion. It is missing from the list. See screencast here: http://screencast.com/t/5Jicyb9ilm5
Comment 1 Mike Krüger 2012-01-12 10:37:11 UTC
Fixed that one. I really wonder why that case wasn't detected by the unit test suite :/

But anyways - it's fixed & added.