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
I'd like to suggest some improvements to make wasmtime-dotnet more AOT friendly. I'm thinking along the lines of enabling static linking against wasmtime, which could really improve scenarios where the C# assembly is AOT compiled.. More details about .NET's native AOT and how it interops with native code can be found here: Native AOT with .NET.
Why This Matters:
AOT offers significant performance improvements and having wasmtime-dotnet support this more seamlessly would be a huge win. It could enhance the library's usability in high-performance scenarios.
Suggested Changes:
Enable static linking in wasmtime-dotnet.
Ensure compatibility with .NET AOT binaries.
I'm happy to implement the necessary changes myself if it is something that will be accepted.
The text was updated successfully, but these errors were encountered:
Hi @andrewmd5, thanks very much for the informational request!
I definitely think this would be something we would accept, but I'm not entirely sure what the work entails. Is it mostly just a different way of building the project?
I'd like to suggest some improvements to make wasmtime-dotnet more AOT friendly. I'm thinking along the lines of enabling static linking against wasmtime, which could really improve scenarios where the C# assembly is AOT compiled.. More details about .NET's native AOT and how it interops with native code can be found here: Native AOT with .NET.
Why This Matters:
AOT offers significant performance improvements and having wasmtime-dotnet support this more seamlessly would be a huge win. It could enhance the library's usability in high-performance scenarios.
Suggested Changes:
I'm happy to implement the necessary changes myself if it is something that will be accepted.
The text was updated successfully, but these errors were encountered: