Clarify wording concerning portable libraries in NonWeb.md #266
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
|
Excellent. Thanks. Could never get quite the right wording myself. This reads well. |
|
lgtm |
lukewagner
added a commit
that referenced
this pull request
Jul 15, 2015
Clarify wording concerning portable libraries in NonWeb.md
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.
This makes two clarifications suggested in #256 concerning NonWeb.md. The first is to dial down the wording about the Loader spec from "intended to be implemented" to "proposed". The second is to be clear that the wasm spec isn't trying to spec any large portability libraries but rather expose the host environment's builtin libraries and allow community-developed libraries to provide portable abstractions.