Jonathan Pobst

The downside to channels is you have to write native code. By the time you're doing that, what value does Xamarin offer? Based on my experience supporting users, I suspect...

> making our binding nuget packages describe the artifact There has been a little bit of work around this for the NuGets we create: https://www.nuget.org/packages/Xamarin.AndroidX.Core It isn't currently used for...

Another possibility might be to use source generators and allow definitions to be provided in C#. It has the same issue as `dynamic` in that it requires "magic strings", but...

> I would have to agree with Jon here. Every participant in this conversation is "Jon", but it seems like you mean @Redth! 😁

> The customers we interact with usually fail with bindings due to tooling on our side and the complexity that goes along with it. I think we need to dive...

Is there a benefit to having both a non-generic **static** marshal method **_AND_** a non-generic **instance** marshal method? It seems like we could use the static invoker to resolve the...

I guess the indirection is only paid for on generic types. Non-generic types could still be done with only the static marshal method. It seems likely that there will be...

I think I successfully implemented my suggestion as a prototype here: https://github.com/jpobst/GenericBindingPrototype/blob/main/Generic-Binding-Lib/Additions/Example.GenericType.cs https://github.com/jpobst/GenericBindingPrototype/blob/main/Generic-Binding-Lib-Sample/MainActivity.cs It uses the "constrain to JLO" method as that seemed easier to implement. It appears to be...

For completeness, I thought I'd explore a reflection based solution (with caching) to determine the performance impact. This method would not require "invoker" interfaces, by adding a single public method...

I think this is the same as: https://github.com/xamarin/java.interop/issues/503