Extract & encapsulate 'InvokeUnmarshalled' in JSInterop

[majda107]

After digging deep into these issues:
#21426
#21444

I've figured out there is a way to invoke unmarshalled js function, making execution many times faster, this comes especially handy if you don't need to encapsulate any objects but only send numeric/string data (like coordinates) speeding up entire thing by so much.

Not something average WebDev may appreciate, but if you need to do something with ~ let's say canvas / js rendering ~ this is a must in order to hit 60fps cap.

If this gets approved by someone, I am definitelly up forking blazor, doing some nice extraction & encapsulation followed by submitting merge request.

You can see demo usage of InvokeUnmarshalled here...
https://blaze.majdatrpkos.cz/ (multi-selected multiple elements with SHIFT and drag them to test performance)
https://github.com/majda107/blaze-cards

wasn't even able to hit solid 60fps before, and that's only CSS transforms rendering, there are potential ways to hook WebGL bindings and stuff so this may really make sense...

[pranavkm]

InvokeUnmarshalled is part of Blazor WASM's supported API surface and we recommend using it in specific performance sensitive code paths. It's not entirely clear what it is that you're suggesting here. Related, Mono's JavaScript APIs that allow reading unmarshalled data isn't stable as yet and is likely to change during the 5.0 release. This might affect callsites such as https://github.com/majda107/blaze-cards/blob/3f3f7069100d2d4a6451a3498490eaf45887d150/BlazeCardsCore/wwwroot/blaze-cards/cards.js#L26.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

[legistek]

InvokeUnmarshalled is part of Blazor WASM's supported API surface and we recommend using it in specific performance sensitive code paths.

Is there any documentation for how to use it properly? In particular on the Javascript side - such as BINDING.conv_string?

And this is probably a noob question, but when we use InvokeUnmarshalled and give it, say, an int[] or float[], is the Mono runtime still making a copy for JS or is JS getting a direct memory pointer at that point? In other words can we not only avoid JSON serialization/deserialization but also memory copying?