diff options
| author | Dan Gohman <sunfish@mozilla.com> | 2015-06-12 14:19:03 -0700 |
|---|---|---|
| committer | Dan Gohman <sunfish@mozilla.com> | 2015-06-15 09:25:20 -0700 |
| commit | 18a5288b99a812b9237f426c1194876afa2362d4 (patch) | |
| tree | 7f35bbf060455e5c316711b219e606bf929fe6a1 /BinaryEncoding.md | |
| parent | 0f08d3363616080b0adeceea87f035980b843046 (diff) | |
| download | nanowasm-design-18a5288b99a812b9237f426c1194876afa2362d4.tar.gz | |
Use https links instead of http links for sites that support it.
Diffstat (limited to 'BinaryEncoding.md')
| -rw-r--r-- | BinaryEncoding.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/BinaryEncoding.md b/BinaryEncoding.md index 3aad2a6..0635a20 100644 --- a/BinaryEncoding.md +++ b/BinaryEncoding.md @@ -27,7 +27,7 @@ Reducing download size, is achieved through three layers: features like constant pools. * Another example is reordering of functions and some internal nodes, which we know does not change semantics, but - [can improve general compression](http://www.rfk.id.au/blog/entry/cromulate-improve-compressibility/). + [can improve general compression](https://www.rfk.id.au/blog/entry/cromulate-improve-compressibility/). * **Generic** compression, such as gzip, already supported in browsers, or LZMA and other compression algorithms, which might be standardized as well. @@ -61,7 +61,7 @@ Yes: ### Variable-length integers * 31% size reduction before compression, 7% size reduction after compression. - * [LEB128](http://en.wikipedia.org/wiki/LEB128) except limited to uint32_t payloads. + * [LEB128](https://en.wikipedia.org/wiki/LEB128) except limited to uint32_t payloads. ## Global structure @@ -113,7 +113,7 @@ having unique names for unique features (and associated [conventions](https://hs The current proposal is to maintain both the efficiency of indices in the [serialized AST](BinaryEncoding.md#serialized-ast) and the established conflict-avoidance practices surrounding string names: * The WebAssembly spec doesn't define any global index spaces - * So, as a general rule, no magic numbers in the spec (other than the literal [magic number](http://en.wikipedia.org/wiki/Magic_number_%28programming%29)). + * So, as a general rule, no magic numbers in the spec (other than the literal [magic number](https://en.wikipedia.org/wiki/Magic_number_%28programming%29)). * Instead, a module defines its *own* local index spaces of opcodes by providing tables *of names*. * So what the spec *would* define is a set of names and their associated semantics. * If the implementation encounters a name it doesn't implement, by default an error is thrown while loading. |