alexcrichton opened PR #4174 from improve-wasmtime-readme
to main
:
This commit is me finally getting back to #2688 and improving the README
of thewasmtime
crate. Currently we have a [pretty drab README][drab]
that doesn't really convey what we want about Wasmtime.While I was doing this I opted to update the feature list of Wasmtime as
well in the main README (which is mirrored into the crate readme),
namely adding a bullet point for "secure" which I felt was missing
relative to how we think about Wasmtime.Naturally there's a lot of ways to paint this shed, so feedback is of
course welcome on this! (I'm not the best writer myself)[drab]: https://crates.io/crates/wasmtime/0.37.0
<!--
Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
alexcrichton edited PR #4174 from improve-wasmtime-readme
to main
:
This commit is me finally getting back to #2688 and improving the README
of thewasmtime
crate. Currently we have a [pretty drab README][drab]
that doesn't really convey what we want about Wasmtime.While I was doing this I opted to update the feature list of Wasmtime as
well in the main README (which is mirrored into the crate readme),
namely adding a bullet point for "secure" which I felt was missing
relative to how we think about Wasmtime.Naturally there's a lot of ways to paint this shed, so feedback is of
course welcome on this! (I'm not the best writer myself)Closes #3707
[drab]: https://crates.io/crates/wasmtime/0.37.0
<!--
Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
abrown submitted PR review.
abrown created PR review comment:
configuration to provide many options such as further means of restricting
cfallin submitted PR review.
cfallin submitted PR review.
cfallin created PR review comment:
as well. We follow best practices for defense-in-depth and known protections and mitigations for issues like Spectre. Finally, we're working to push the state-of-the-art: we are collaborating with academic researchers to formally verify critical parts of Wasmtime and Cranelift.
alexcrichton updated PR #4174 from improve-wasmtime-readme
to main
.
alexcrichton edited PR #4174 from improve-wasmtime-readme
to main
:
This commit is me finally getting back to #2688 and improving the README
of thewasmtime
crate. Currently we have a [pretty drab README][drab]
that doesn't really convey what we want about Wasmtime.While I was doing this I opted to update the feature list of Wasmtime as
well in the main README (which is mirrored into the crate readme),
namely adding a bullet point for "secure" which I felt was missing
relative to how we think about Wasmtime.Naturally there's a lot of ways to paint this shed, so feedback is of
course welcome on this! (I'm not the best writer myself)Closes #3704
Closes #3707[drab]: https://crates.io/crates/wasmtime/0.37.0
<!--
Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
cfallin submitted PR review.
alexcrichton merged PR #4174.
Last updated: Dec 23 2024 at 12:05 UTC