Bug 31941 - Don't create empty _Extensions classes in the generator
Summary: Don't create empty _Extensions classes in the generator
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 8.99 (iOS9 previews)
Hardware: PC Mac OS
: --- minor
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-07-14 15:21 UTC by Larry O'Brien
Modified: 2015-07-29 09:07 UTC (History)
3 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 Larry O'Brien 2015-07-14 15:21:54 UTC
MonoTouch.Foundations.NSDiscardable_Extensions does not seem to define any members, at least as far as the API docs XML is concerned.
Comment 1 Larry O'Brien 2015-07-14 15:22:22 UTC
Comment 2 Rolf Bjarne Kvinge [MSFT] 2015-07-16 05:42:23 UTC
This is a more general problem, we do this for all protocols that don't have any optional members.

@Alex, can you have a look at this (it's low priority, lower than anything iOS9/OSX10.11 related), it should just be a matter of checking there are any members to print before printing the class itself.
Comment 3 Sebastien Pouliot 2015-07-29 09:07:28 UTC
Those empty _Extensions types are (already) not generated for the unified assemblies.

However it's (technically*) a breaking change for classic (type removal) so the generator still emit them.

* not very likely to cause issues but we have seen many other non-likely cases bite us back over the years