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 for Bug 44582 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
This PR pointed out that Apple now has enums with different values in 32-bit and 64-bit
Unchecked code should be fine for unsigned values, but not for signed:
csharp> unchecked ((uint) ulong.MaxValue == uint.MaxValue);
csharp> unchecked ((int) long.MaxValue == int.MaxValue);
we already have some code for return values: https://github.com/xamarin/xamarin-macios/blob/master/src/generator.cs#L3879-L3887
Better link for return values: https://github.com/xamarin/xamarin-macios/blob/39d903ab663282d30668dd1d1d16329803116b71/src/generator.cs#L3835-L3848
> we should detect them first (xtro?) and see how to expose them correctly
Honestly I'm not sure how to handle them yet - but we need to know them first.
If there's only a few we could add some helper (extension ?) methods like:
> value.IsUnknown ()
that will check an integer (int or long) value depending if run on 32 or 64 bits OS.