Fork of https://github.com/WebAssembly/design/ with NanoWasm extensions. https://gitea.privatedns.org/xavi/nanowasm-design/atom?h=main 2018-03-08T18:49:44+00:00 2018-03-08T18:49:44+00:00 YHSPY Becavalier@users.noreply.github.com 2018-03-08T18:49:44+00:00 urn:sha1:1be8b3b3115b971b5961ea0f7f07938783160f08 2017-11-15T16:48:14+00:00 Joseph Richey joerichey@google.com 2017-11-15T16:48:14+00:00 urn:sha1:e2be77eaac770268a4c22fb09c6f648de7b9b6b8 This link standardizes how all the other design pages will refer to future features (either in `FutureFeatures.md` or in a tracking issue). All links to these upcoming features now use references at the bottom of the doc page (as opposed to inline links or references). Note that this change makes it very easy for the doc links to be updated when a tracking issue is started. As all the references have a standard format; a simple find/replace script will get everything. This commit also makes sure that references now point to a tracking issue if one exists. Note that this means a future CL can now delete some of the unnecessary sections from `FutureFeatures.md`. The only visible change from this commit is that certain broken links are now fixed, or links pointing to a doc section now point to the correct tracking issue. 2017-07-21T18:45:26+00:00 hubert-reinterpretcast hubert-reinterpretcast@users.noreply.github.com 2017-07-21T18:45:26+00:00 urn:sha1:fb384b991f50deff4c8d7a7301307d1463a3ae64 Redirected a link on ES6 module integration to the future features page. 2017-06-02T21:48:01+00:00 JF Bastien github@jfbastien.com 2017-06-02T21:48:01+00:00 urn:sha1:95f3da4b3d5d417181a4581fb73e1aff14efd65e Now tracked by: #1087 As discussed here: #1066 2017-03-30T16:33:19+00:00 Dan Gohman sunfish@mozilla.com 2017-03-30T16:33:19+00:00 urn:sha1:8e5ecc3614135a7da011cc4730e227fcb9021494 * Require import/export names to be UTF-8. This implements the UTF-8 proposal described in https://github.com/WebAssembly/design/issues/989#issuecomment-284757788. This does not currently rename "name" to "utf8-name", because if UTF-8 is required for import/export names, there's a greater appeal to just saying that all strings are UTF-8, though this is debatable. * s/utf8/UTF-8/g * Say "UTF-8 byte sequence" rather than "UTF-8 string". This document is describing the encoded bytes, rather than the string which one gets from decoding them. Also, make the descriptions of the byte sequence length fields more precise. * Fix typo. 2016-12-29T21:50:00+00:00 JF Bastien github@jfbastien.com 2016-12-29T21:50:00+00:00 urn:sha1:a9ccc82e2ab9db3af1acb30ec70cda82e1f30803 * Export name uniqueness spec test exports.wast makes it a validation failure for exported names to be duplicate. I find this somewhat surprising (I see exports as a dictionary, so duplicates simply overwrite previous entries), I'd therefore be happy if others want to reverse the polarity of this (make it OK to duplicate export names). * Fix unintended change 2016-12-14T17:22:39+00:00 rossberg-chromium rossberg@chromium.org 2016-12-14T17:22:39+00:00 urn:sha1:a87e58c34107a44da2e3c86e3e12de669ee3b30d 2016-12-14T17:08:25+00:00 JF Bastien github@jfbastien.com 2016-12-14T17:08:25+00:00 urn:sha1:b4525659723e42fac2f44322f413e2cfc026d387 * Start function clarifications Resolves #896. * Clarify 2016-11-14T23:19:00+00:00 JF Bastien github@jfbastien.com 2016-11-14T23:19:00+00:00 urn:sha1:8feef4c3b6bf8dc21b6b27ff2e528b4cf772307b * Function index space is used by exports * Mention start function as well * Elements 2016-11-03T13:37:25+00:00 Luke Wagner mail@lukewagner.name 2016-11-03T13:37:25+00:00 urn:sha1:97b4ec76ff6360c59669be5838bb329988f64a25 * Clarify names section indexing * Fix broken link * Link start-section to Modules.md#function-index-space link * Explicate index spaces * Periods