-
Notifications
You must be signed in to change notification settings - Fork 18.3k
Open
Labels
FeatureRequestIssues asking for a new feature that does not need a proposal.Issues asking for a new feature that does not need a proposal.NeedsDecisionFeedback is required from experts, contributors, and/or the community before a change can be made.Feedback is required from experts, contributors, and/or the community before a change can be made.OS-JSarch-wasmWebAssembly issuesWebAssembly issues
Milestone
Description
At present, when we compile to wasm syscall/js
is automatically included.
This forces the runtime to either be a browser (eg Firefox, Chrome, etc), or at least pretend to be one.
That's kind of non-optimal, as some of the wasm execution environments presently being developed aren't targeted at browser environments. eg:
- https://github.com/Xe/olin
- https://github.com/ewasm/hera
- https://github.com/perlin-network/life
- https://github.com/cervus-v/cervus
- https://github.com/go-interpreter/wagon
- https://github.com/paritytech/wasmi
- https://github.com/nebulet/nebulet
- https://github.com/WAVM/WAVM
- https://github.com/cranestation/wasmtime
In the WebAssembly Gophers Slack channel we have people asking about non-browser use cases fairly often. It seems likely that'll be a fairly standard use case, if it can be catered to as well.
How feasible would it be to have some way to suppress the default syscall/js
inclusion, or otherwise make it optional?
Xe, dennwc, theclapp, zfsamzfsam, GeorgeHahn and 15 moresmasher164, trashhalo, awfulcooking and brooksmtownsend
Metadata
Metadata
Assignees
Labels
FeatureRequestIssues asking for a new feature that does not need a proposal.Issues asking for a new feature that does not need a proposal.NeedsDecisionFeedback is required from experts, contributors, and/or the community before a change can be made.Feedback is required from experts, contributors, and/or the community before a change can be made.OS-JSarch-wasmWebAssembly issuesWebAssembly issues