Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Some classes aren't meant to be subclassed (based on their documentation).
Example: RPScreenRecorder , there's a sharedInstance property that returns the only valid instance.
Making classes sealed also:
* Makes us able to generate less code for the bound methods (they don't have to be virtual, and can assume nobody will override them, so their implementation can be simpler)
* Makes the registrar able to just skip those types completely, no processing needed.
Unfortunately the generator completely ignores the [Sealed] attribute on types, it's only honored on methods.
Merged in master https://github.com/xamarin/xamarin-macios/commit/44f14cf768f0ab82b185eb03cd4053a7da403b96