Bug 1799 - [New Resolver] Invalid code completion when typing name of variable
Summary: [New Resolver] Invalid code completion when typing name of variable
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-10-31 12:04 UTC by Lluis Sanchez
Modified: 2011-11-08 05:00 UTC (History)
1 user (show)

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 Lluis Sanchez 2011-10-31 12:04:30 UTC
The code completion window is shown in auto commit mode when I start typing the name of a variable. That's incorrect because it forces me to select one of the entries, so for example if I try to type "int n;" I end typing "int new;".
Comment 1 Mike Krüger 2011-11-01 05:13:44 UTC
should be fixed by a prior patch.

But I added some unit tests for that context & improved the handling of it.
Comment 2 Lluis Sanchez 2011-11-07 06:32:28 UTC
I can still reproduce this problem in some cases. See http://screencast.com/t/2yK8MUfWAh4
Comment 3 Mike Krüger 2011-11-08 05:00:23 UTC
In that context the for statement was the problem - the syntax error there caused a wrong lookup and the context got treated as for condition context. 

The best solution for improving the detection of syntax errors is adding syntax errors to the Ast - this context now works.