Bug 4487 - Filtering possible types for new expressions a bit too aggressively
Summary: Filtering possible types for new expressions a bit too aggressively
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-04-17 18:06 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2012-04-18 04:56 UTC (History)
2 users (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 Rolf Bjarne Kvinge [MSFT] 2012-04-17 18:06:07 UTC
See repro of how I try to create an instance of NSString:


"var foo = NSSt" works

"string bar = new NSStr" does not.

Note that the eventual idea is to write this:

"string var = new NSString (<intptr>).ToString ();"
Comment 1 Mikayla Hutchinson [MSFT] 2012-04-17 18:59:54 UTC
Hm, that's a good point. It's an odd pattern, but it's valid C#, so the completion engine can't really filter the types there at all.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2012-04-17 19:14:18 UTC
I think it should pre-select "string" in the above sample (but still list all the other types).
Comment 3 Mikayla Hutchinson [MSFT] 2012-04-17 19:48:47 UTC
Well, selecting the exact type "string" is what it does already, it can still do this in suggestion mode although the selection will not be solid.

Another idea, IIRC we currently filter to all valid subtypes, maybe we could keep this filtering available by categorizing the list - subtypes vs. all other types?
Comment 4 Mike Krüger 2012-04-18 04:56:05 UTC
fixed - the categorizing was a good idea btw.
(Even if I think I will not use it much)