We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
See also wasm-tool/rust-plugin#1 and #153
Basically there are four main options:
Should we snip the std::panicking code? yes/no
std::panicking
Should we snip the std::fmt code? yes/no
std::fmt
Here are some specific functions to snip. (list of zero or more strings)
Here are some regex patterns of functions to snip. (list of zero or more strings)
The text was updated successfully, but these errors were encountered:
following up on this feature request- do we still want to do this? how do we want to prioritize this?
Sorry, something went wrong.
do we still want to do this?
Yes, I believe so.
how do we want to prioritize this?
Not super high, in my opinion. I think the existing RFCs, wasm-opt support, and serve/watch are probably all higher priority.
wasm-opt
serve
watch
Successfully merging a pull request may close this issue.
See also wasm-tool/rust-plugin#1 and #153
Basically there are four main options:
Should we snip the
std::panicking
code? yes/noShould we snip the
std::fmt
code? yes/noHere are some specific functions to snip. (list of zero or more strings)
Here are some regex patterns of functions to snip. (list of zero or more strings)
The text was updated successfully, but these errors were encountered: