Bug 4498 - Implement implicit handles generic interfaces badly
Summary: Implement implicit handles generic interfaces badly
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: Lowest enhancement
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-04-18 09:38 UTC by Alan McGovern
Modified: 2012-07-18 06:44 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 2012-04-18 09:38:23 UTC
If i have a class implementing IEnumerable<IUndoAction> and i choose to implement that interface implicitly, the code generation implements this:

public System.Collections.IEnumerator GetEnumerator ()
	throw new System.NotImplementedException ();

IEnumerator<IUndoAction> IEnumerable<IUndoAction>.GetEnumerator ()
	throw new System.NotImplementedException ();

It should implement them the other way around so the typed method is the implicit one and the untyped method is the explicit one.
Comment 1 Mike Krüger 2012-07-18 06:44:48 UTC