Fork of https://github.com/WebAssembly/design/ with NanoWasm extensions. https://gitea.privatedns.org/xavi/nanowasm-design/atom?h=main 2020-01-14T01:05:51+00:00 2020-01-14T01:05:51+00:00 Kenrick kenrick95@gmail.com 2020-01-14T01:05:51+00:00 urn:sha1:376bcc4b9cba79280d79be023d71e30d0b00ba47 * Fix broken links to GC.md * Update links to proposals repo 2018-05-04T16:47:20+00:00 Romario Maxwell romario.maxwell@gmail.com 2018-05-04T16:47:20+00:00 urn:sha1:2614fd32d8d4a099fca021d1e880a9d9d8e848e8 All the modified URLs were checked to see if they are available over HTTPS by opening a new tab in the browser, entering the URL in the address bar, changing http:// to https:// and then verifying if the resource displayed is the same over HTTP and HTTPS for each URL. 2018-01-02T15:07:26+00:00 JF Bastien github@jfbastien.com 2018-01-02T15:07:26+00:00 urn:sha1:6bf6fa02ac3a8a1de4907c2b22fd364f4e5a38d3 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-05-17T15:38:27+00:00 rossberg-chromium rossberg@chromium.org 2017-05-17T15:38:27+00:00 urn:sha1:abb557a97d672393aabba2f6fb9254a5ed95f60e 2017-02-03T14:34:37+00:00 Dan Gohman sunfish@mozilla.com 2017-02-03T14:34:37+00:00 urn:sha1:408cdd8b8bfabfe158df22969da2b15c1e05afec * Explain why NaN bitpatterns are nondeterministic. NaN bits are a surprising thing to see in Nondeterminism.md, given how deterministic WebAssembly is otherwise. This PR adds some explanation to Rationale.md. This is meant to finish https://github.com/WebAssembly/design/issues/619. * Clarify "should" by saying "(as opposed to shall)". * Mention globals and linear memories as ways that NaN bitpatterns can be observed. And clarify the wording in a few other places. 2017-01-26T00:35:36+00:00 Dan Gohman sunfish@mozilla.com 2017-01-26T00:35:36+00:00 urn:sha1:f633459b736cde57017897d1630951f03119caf5 * Rationale: document that NaNs in JS are not necessarily canonicalized. This also tidies up the wording of the NaN section in the rationale somewhat. This is aimed at addressing #746. * Fix spelling: noncanonical -> non-canonical 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