-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dotnet] [bidi] Expand usability of CallFunctionAsync<TResult>
and EvaluateAsync<TResult>
#15442
base: trunk
Are you sure you want to change the base?
Conversation
…`EvaluateAsync<TResult>`
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
Per conversation on Slack:
Yes, this is AOT-safe. It doesn't root any types that wouldn't certainly be rooted in else where, and patterns like |
Description
Greatly expands usability of two methods which de-serialize BiDi types to .NET types
Test suite demonstrates the full extent, here is an example
Motivation and Context
The two methods can be much more usable
Types of changes
Checklist