Add a WASI design principles document. #192
Merged
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
tlively
reviewed
Jan 7, 2020
kripken
reviewed
Jan 7, 2020
eddyp
reviewed
Jan 7, 2020
sbc100
reviewed
Jan 7, 2020
This was referenced Jan 10, 2020
This spells out WASI's design principles around capabilities, relationship to POSIX, and other topics. This also includes a section on virtualization, which takes some ideas from WebAssembly#69, but modifies it to focus on using interface types and the linking proposal to implement virtualization.
sunfishcode
force-pushed
the
design-principles
branch
from
7d6a36e to
ef3c55f
Compare
…rgeable capabilities.
frzifus
reviewed
Feb 8, 2020
Fix spelling of "trade-off" Co-Authored-By: Ben B. <[email protected]>
|
Thanks to everyone who reviewed this! I've addressed all the feedback, and there were no major objections, so I'll proceed to merge this. Feedback is still welcome; please file issues to ask questions or make comments, or even feel free to submit PRs to suggest changes. |
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.
As part of a larger effort to answer questions about what capability-based design means, whether WASI is intending to be POSIX-oriented, and other things, here's a draft of a design principles document.
This also includes a section on virtualization, which takes some ideas from #69, but modifies it to focus on using interface types and the linking proposal to implement virtualization.
Feedback is welcome!
Edit: Click here to read as rendered html