Fork of https://github.com/WebAssembly/design/ with NanoWasm extensions. https://gitea.privatedns.org/xavi/nanowasm-design/atom?h=main 2017-11-15T16:48:14+00:00 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. 2016-10-30T16:22:33+00:00 Brad Nelson flagxor@gmail.com 2016-10-30T16:22:33+00:00 urn:sha1:18759dd1f259429504cba1b9470744f5135db7b4 2016-10-28T03:58:36+00:00 Brad Nelson flagxor@gmail.com 2016-10-28T03:58:36+00:00 urn:sha1:93e4e3b2d27884bf0cc989bed4f1161074804ada Added brief item on multiple return. 2016-10-26T20:52:58+00:00 Seth Thompson s3th.thompson@gmail.com 2016-10-26T20:52:58+00:00 urn:sha1:cad0ea9ed5f0ac1dda62abe2c66d0a38ff8c104d 2016-07-12T04:34:03+00:00 Dominic Chen d.c.ddcc@gmail.com 2016-07-12T04:34:03+00:00 urn:sha1:62f30968a641ef6eb7f8cceadae232cea4ad7b4a This commit introduces a discussion of WebAssembly's security model for both users and developers, though primarily targeted at latter. Resolves #205. 2016-06-28T16:45:04+00:00 Luke Wagner mail@lukewagner.name 2016-06-28T16:45:04+00:00 urn:sha1:56e617e8144a8b750a1198871eb6d43fad182c21 * Add Memory, Table and multi-import/export of these * Clarify mutation of elements * Mention CFI use case * Clarify call_table signature mismatches * Explicate elements section * Change support to allow/enable * Remove table/memory indices add global imports/exports * Clarify host-defined (i.e., JavaScript) table elements * s/necessary/useful * s/will/may/ * Fix typo * Fix typo * Clarify that table updates are observed by all instances * Clarify that host-defined table element values can have different signature checking * Just 'constraints' since more detail is below * Wordsmith DynamicLinking.md intro * Wordsmith FutureFeatures.md * Try to clarify wording in FutureFeatures.md * Change 'function' to 'anyfunc' * Fix nits * Refine description of initializer expressions * Remove the Definition Index Space, use (type, index) pairs as necessary 2016-04-28T18:33:26+00:00 Dan Gohman sunfish@mozilla.com 2016-04-28T18:33:26+00:00 urn:sha1:149a43b3124ed9d7a8385757976f766324ab4c80 * Permit implementations to return canonical NaNs from arithmetic. RISC-V and ARM in "default NaN" mode do not propagate NaN values in arithmetic operations. Instead, they return a "canonical" NaN. IEEE 754 doesn't require NaN propagation; it's merely a "should". In order to ensure that wasm doesn't accidentally over-burden support for the above and other potential future IEEE-754-conforming platforms, this patch changes the NaN rules to permit either behavior. * Add the IEEE 754 section number for the NaN propagation recommendation. * Avoid "typically". * Reword the NaN conversion rules for clarity. 2016-03-31T23:20:22+00:00 JF Bastien github@jfbastien.com 2016-03-31T23:20:22+00:00 urn:sha1:832e67b370c38353fdf19136c205cd97d015ee8a 2016-03-31T22:37:53+00:00 JF Bastien github@jfbastien.com 2016-03-31T22:37:53+00:00 urn:sha1:675eee78ea4613025ec3bd12f0020609bfb8c81a As discussed in https://github.com/WebAssembly/design/pull/629#discussion_r58138148 2016-02-18T19:55:40+00:00 Dan Gohman sunfish@mozilla.com 2016-02-18T19:55:40+00:00 urn:sha1:aea48078aef9fbcaf52b3f728c2231b2fe375437