diff options
| author | JF Bastien <github@jfbastien.com> | 2015-06-04 13:34:50 -0700 |
|---|---|---|
| committer | JF Bastien <github@jfbastien.com> | 2015-06-04 13:34:50 -0700 |
| commit | a6272b1c5d7219bd1ba8e6452ac0b905a2e95acf (patch) | |
| tree | 3748ecb7ff5e235336cf798bafbf18ec85a97e82 /BinaryEncoding.md | |
| parent | 5510bdf079057f42ff35511108c4db50196d540d (diff) | |
| parent | d94d55d8a900fa507ecfc59d37bba0ff33b70271 (diff) | |
| download | nanowasm-design-a6272b1c5d7219bd1ba8e6452ac0b905a2e95acf.tar.gz | |
Merge pull request #111 from WebAssembly/polyfill-js
Polyfill to JavaScript
Diffstat (limited to 'BinaryEncoding.md')
| -rw-r--r-- | BinaryEncoding.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/BinaryEncoding.md b/BinaryEncoding.md index a01f423..e605ea5 100644 --- a/BinaryEncoding.md +++ b/BinaryEncoding.md @@ -13,7 +13,7 @@ it as having three layers: compression algorithm like gzip to achieve. * This is not meant to be standardized, at least not initially, as it can be done with a downloaded decompressor that runs as web content on the client, and in particular - can be implemented in the polyfill. Not standardizing it leaves the binary + can be implemented in a polyfill. Not standardizing it leaves the binary encoding as the only thing a WebAssembly implementation is required to implement, which is nice. However, if the benefits are shown to be substantial, this will be reconsidered in the future. |