Bug 2217 - Missing options when generic and non generic types clash
Summary: Missing options when generic and non generic types clash
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-11-28 06:58 UTC by Alan McGovern
Modified: 2012-02-07 03:16 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 Alan McGovern 2011-11-28 06:58:07 UTC
There are many variants of the 'Tuple' class. MD does not enumerate the generic and non generic versions when writing code like:

Tuple<string, int,

As i add more information it should realise that I want the generic version on line 2 and so show me completion for Tuple<T>. On line three because i've entered one parameter it should then give me completion for Tuple<T1, T2>, etc.
Comment 1 Mike Krüger 2012-02-07 03:16:13 UTC