Bug 4653 - [New Resolver] Autocomplete lists variables that do not exist in the current context
Summary: [New Resolver] Autocomplete lists variables that do not exist in the current ...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 2.9.x
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-04-25 17:16 UTC by lindsey.driscoll
Modified: 2012-05-03 10:29 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 lindsey.driscoll 2012-04-25 17:16:06 UTC

When calling a method that has a set of parameters, the autocompletion displays the name of the current parameter as a viable option to select, even if it does not exist in the current context.




MacOSX: Lion
MD: 2.9.6 (revision-da6068e783f7620fdb6879fc89320a185d9e2b9b)
Mono: 2.10.9
Comment 1 Mike Krüger 2012-04-26 01:11:36 UTC
Named arguments:

Comment 2 Mikayla Hutchinson [MSFT] 2012-04-26 13:53:03 UTC
It is quite confusing.

VS disambiguates them with a trailing colon: http://stackoverflow.com/questions/4994637/named-parameters-in-c-sharp-4-and-intellisense
Comment 3 Mikayla Hutchinson [MSFT] 2012-04-27 11:12:56 UTC
This is a bug, not an enhancement. They are displayed exactly the same as locals, which is confusing.
Comment 4 Mike Krüger 2012-05-03 10:29:43 UTC

It's not really confusing - I always know what I want/can type there and not waiting minutes in that context and be 'confused'. I think that people who find the old one confusing may be now even more confused because of the ':' - they don't know about the named argument call :)

But yes adding ':' is an enhancement there - we can need maybe another icon for that. 

I would like to have a different icon for parameters - that would really be helpful.