-
Notifications
You must be signed in to change notification settings - Fork 2.7k
make the default wasm execution method compiled #8847
Conversation
This is not correct. What you are citing there is the substrate node. The rest of the code is still not enabling the feature automatically. I think we should remove the feature now completely and have wasmtime enabled all the time, automatically. @pepyakin WDYT? |
Can we instead just enable these features by default at the crates that declare them and do not remove them? This would allow to build nodes without wasmtime. That seems to be somewhat useful since wasmtime is a big dependency. Not sure if that's a realistic need though. I am ok with removing the feature altogether since that would reduce the complexity. |
The problem with enabling |
Looks like the wasm build is currently failing because |
The |
Alternative approach: #8855 |
While this wasn't the reason the feature was introduced, it is now a valid reason to keep it :D |
#8855 is the better way forward. |
This promotes using
wasmtime
instead ofwasmi
for the majority of users.Note: this PR removes the
wasmtime
feature entirely, and includes that dependency always.Previous note, now obsolete:
in principle it is possible for this default to result in a panic shortly after startup if a user has compiled their node without the.wasmtime
feature