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
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
I've successfully used this tool for Dark, yielding a single .wasm file - awesome!
Currently, dotnet-wasi-sdk doesn't seem to respect the RunAOTCompilation.
Is there a way to adjust the project to respect it? Or maybe I'm incorrect in hoping for that flag to be respected here.
The text was updated successfully, but these errors were encountered:
I agree! That's definitely something we should add support for. In my estimation, most production deployments should use AOT since the additional file size isn't really much of a drawback, and the additional speed gain is definitely valuable.
No specific ETA for implementing this, though I'd certainly take a PR if you're able to figure it out. It's not easy to figure out though.
Unfortunately, I have no idea where to start here. :)
If you provide some initial pointers, I'll know if I have the background/energy to pursue it.
If not, at least we can provide the future implementer some initial notes!
I've successfully used this tool for Dark, yielding a single
.wasm
file - awesome!Currently,
dotnet-wasi-sdk
doesn't seem to respect theRunAOTCompilation
.Is there a way to adjust the project to respect it? Or maybe I'm incorrect in hoping for that flag to be respected here.
The text was updated successfully, but these errors were encountered: