docs/HighLevelGoals.md: mention motivations behind WASI-crypto #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ueno
force-pushed
the
wip/dueno/motivations
branch
2 times, most recently
from
c711bdc
to
5f16b32
Compare
|
Excellent! And that was much needed, thank you! |
Maybe change to "not currently possible"? There is hope that it can be fixed at WebAssembly level. |
This adds a new section describing why WASI-crypto is needed, before going into the goals definition.
ueno
force-pushed
the
wip/dueno/motivations
branch
from
5f16b32
to
e47f1cc
Compare
|
Thanks, updated. |
|
Looking great! Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I realized that there are no written references to our motivations behind WASI-crypto. I've tried to collect them from the discussions in WebAssembly/WASI#65 and bytecodealliance/wasmtime#71.