diff options
| author | JF Bastien <jfb@chromium.org> | 2015-06-04 13:09:12 -0700 |
|---|---|---|
| committer | JF Bastien <jfb@chromium.org> | 2015-06-04 13:09:12 -0700 |
| commit | e5ae3cf844ded15daada4dbaf4afff90ffee4c05 (patch) | |
| tree | 79ba2afb0ce5c05396b22f3d146f65261f5fcfef /BinaryEncoding.md | |
| parent | cd35f9b39f4d8bc186ea8b8fb889dc451113b8d7 (diff) | |
| download | nanowasm-design-e5ae3cf844ded15daada4dbaf4afff90ffee4c05.tar.gz | |
Refactor polyfill quite a bit.
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. |