[GH-ISSUE #39] Use Reflection.Emit for object invocation. #19

New issue

Closed

opened 2026-05-05 10:59:33 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 10:59:33 -06:00

Owner

Originally created by @pauldotknopf on GitHub (Jul 25, 2018).
Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/39

This will give us a huge performance boost.

Using what we've learned in #36, we should not send callbacks to the native world.

Instead, every NetMethodInfo and NetPropertyInfo will have a unit long Id. This id will be used to lookup cached dynamic methods that perform as little as possible.

For example:

public void Invoke(IntPtr t, IntPtr m, IntPtr p, IntPtr r)
{
    using (var method = new NetMethodInfo(m))
    using (var target = new NetReference(t))
    using (var parameters = new NetVariantList(p))
    using (var result = r != IntPtr.Zero ? new NetVariant(r) : null)
    {
        // This will be dynamically compiled!
        ((SomeClass) target.Instance).WithMethodWithStringIntParameters(parameters.Get(0).String, parameters.Get(1).Int);
    }
}

The same thing can be done with property reading/setting.

Originally created by @pauldotknopf on GitHub (Jul 25, 2018). Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/39 This will give us a huge performance boost. Using what we've learned in #36, we should not send callbacks to the native world. Instead, every ```NetMethodInfo``` and ```NetPropertyInfo``` will have a unit ```long Id```. This id will be used to lookup cached dynamic methods that perform as little as possible. For example: ```c# public void Invoke(IntPtr t, IntPtr m, IntPtr p, IntPtr r) { using (var method = new NetMethodInfo(m)) using (var target = new NetReference(t)) using (var parameters = new NetVariantList(p)) using (var result = r != IntPtr.Zero ? new NetVariant(r) : null) { // This will be dynamically compiled! ((SomeClass) target.Instance).WithMethodWithStringIntParameters(parameters.Get(0).String, parameters.Get(1).Int); } } ``` The same thing can be done with property reading/setting.

gitea-mirror closed this issue

2026-05-05 10:59:35 -06:00

gitea-mirror commented

2026-05-05 10:59:37 -06:00

Author

Owner

@RichiCoder1 commented on GitHub (Aug 10, 2018):

Just in case you're interested:

With Refit, it allows you to define an interface and add attributes to it, and then Refit generates the meat of the code (either using a standalone app or an msbuild task).

Refit does this by scanning the source files using Roslyn, and then generating output files (again using roslyn/template files).
https://github.com/reactiveui/refit/blob/master/InterfaceStubGenerator.Core/InterfaceStubGenerator.cs

@RichiCoder1 commented on GitHub (Aug 10, 2018): Just in case you're interested: With Refit, it allows you to define an interface and add attributes to it, and then Refit generates the meat of the code (either using a standalone app or an msbuild task). Refit does this by scanning the source files using Roslyn, and then generating output files (again using roslyn/template files). https://github.com/reactiveui/refit/blob/master/InterfaceStubGenerator.Core/InterfaceStubGenerator.cs

gitea-mirror commented

2026-05-05 10:59:39 -06:00

Author

Owner

@pauldotknopf commented on GitHub (Aug 10, 2018):

Oh, wow! I was wondering how they supported Xamarin where it does AOT compilation. Turns out, they aren't using Reflection.Emit!

I haven't thought about an approach like this. I'm not sure how it would look in Qml.Net.

@pauldotknopf commented on GitHub (Aug 10, 2018): Oh, wow! I was wondering how they supported Xamarin where it does AOT compilation. Turns out, they aren't using Reflection.Emit! I haven't thought about an approach like this. I'm not sure how it would look in Qml.Net.

gitea-mirror commented

2026-05-05 10:59:41 -06:00

Author

Owner

@RichiCoder1 commented on GitHub (Aug 10, 2018):

Absolutely. Figured I'd at least mention it just in case it's applicable :). And would work with AOT restrictions on mobile platforms if/when you got there.

@RichiCoder1 commented on GitHub (Aug 10, 2018): Absolutely. Figured I'd at least mention it just in case it's applicable :). And would work with AOT restrictions on mobile platforms if/when you got there.