You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When converting to a modern .NET runtime, this library should support AOT scenarios.
Describe the solution you'd like
Ensure all libraries for .NET support AOT scenarios. (All samples should support [And test] publish to native AOT to verify functionality)
With a STRONG emphasis on performance the new P/Invoke Source Generation support in .NET allows for a more flexible AOT compatible interop while also opening the door for more performant interop with "lazy" marshalling (especially for strings). The code does NOT need to marshal from native to managed and then back to native again if it already has the native form. Caching of the conversions is plausible and deferring the conversions to as late as possible combine to make a much more efficient system.
Additional context
It is currently unclear how AOT scenarios are testable as it appears that tests don't support that. (The test host framework isn't AOT as it needs to dynamically load and discover tests etc...)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When converting to a modern .NET runtime, this library should support AOT scenarios.
Describe the solution you'd like
Ensure all libraries for .NET support AOT scenarios. (All samples should support [And test] publish to native AOT to verify functionality)
With a STRONG emphasis on performance the new P/Invoke Source Generation support in .NET allows for a more flexible AOT compatible interop while also opening the door for more performant interop with "lazy" marshalling (especially for strings). The code does NOT need to marshal from native to managed and then back to native again if it already has the native form. Caching of the conversions is plausible and deferring the conversions to as late as possible combine to make a much more efficient system.
Additional context
It is currently unclear how AOT scenarios are testable as it appears that tests don't support that. (The test host framework isn't AOT as it needs to dynamically load and discover tests etc...)
The text was updated successfully, but these errors were encountered: