Jonathan Pryor
Jonathan Pryor
@cncb-gh: How are you observing this error? It looks like you have `$(TreatWarningsAsErrors)` disabled: https://github.com/Baseflow/ExoPlayerXamarin/blob/5214b7158fc6611f602ffc0f0122429a3ae49b6d/Directory.Build.props#L22 We should only be emitting a warning for this, and probably not even a warning…...
Another option for `GetValueScope` is to _inhibit_ exception marshaling: Xamarin.Forms has a request to just have the app _exit_ if an exception is thrown, because it **Can't Happen**, and if...
WRT inhibiting exception marshaling, the whole concern was around needing to have *two* JNI invocations "everywhere", e.g. https://github.com/xamarin/java.interop/blob/main/tests/invocation-overhead/jni.cs#L6095-L6099 (in which `JniEnvironment.GetExceptionForLastThrowable()` called `JNIEnv::ExceptionOccurred()` occurred.) Calling through the delegates is not...
> Classes implementing interface methods. This can be supported via explicit interface implementation: ```csharp interface ICloneable { object Clone(); } class MyClass : ICloneable { object ICloneable.Clone() {return Clone(); }...
> Arrays (`object[]` -> string[]`) This worked for me? ```csharp class A { public virtual object[] M() {return null;} } class B : A { public override string[] M() {return...
> Unknown concern \#1: what does this do with assembly versioning? If e.g. Mono.Android.dll v12 embraces covariant return types such that StringBuilder.Append() now returns StringBuilder instead of IAppendable, will that...
@jpobst: with [this in mind](https://github.com/xamarin/java.interop/issues/649#issuecomment-791074127), how crazy/impossible would it be to *prototype* covariant return type support in `generator` to see if we *could* release for .NET 6? If there *were*...
Related: https://github.com/mono/mono/issues/14190 The crash appears to happen because we're trying to do a GC during process shutdown. Possible WorkAround: Don't Do That™. If we could tell if mono were shutting...
This isn't a question around `ScrollingView`; we can't bind a type that we know nothing about, and a "dummy stripped `ScrollingView`" would do more harm than good. The question is...
> It's not in every scenario right? (I got 1 binding binding project where the types 100% resolvable, yet types are going missing during binding without XA warnings) I would...