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 60355 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
The native CGAffineTransform has a "concatenating" method while the Xamarin.iOS CGAffineTransform uses the name "Multiply".
It's preferable that the names of the Xamarin.iOS methods match the native names so that documentation is easier to understand when working with Xamarin.iOS.
We usually prefer .NET-like APIs over copying Apple blindly.
There are a lot of .NET APIs which use "Multiply".
I'd like other team members feedback before closing this. In any case this would be a breaking change the the impact of the change is very low.
In my math courses I never heard about "matrix concatenation", it was always "matrix multiplication", so I think "Multiply" is a much more logical name.
That said, I'm open to adding a "Concat" method that just calls "Multiply". That would also be backwards-compatible, since it's just a new method.
I wonder if this is something we can do with extensions once (if?) C# has support for "extension everywhere" (https://github.com/dotnet/csharplang/issues/192)