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 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-19T19:23:19+00:00 Domenic Denicola d@domenic.me 2017-06-14T20:38:37+00:00 urn:sha1:712729b9118814c0cad5dff41947e0d05bb363d8 Fixes #1081 by being very clear about the interaction with the event loop, i.e. which portions of the tasks happen in parallel and how they get back to the main thread, where objects can actually be created. In general this also makes the specification algorithmic, links it to appropriate definitions, and makes various failure cases (such as being passed a rejected promise, or attempting to read from a locked/disturbed body) clearer. 2017-06-01T14:59:51+00:00 Mircea Trofin mtrofin@google.com 2017-06-01T14:59:51+00:00 urn:sha1:39728da021356dec373fa50d01ec8505696d0108 Clarified that "support" means "presence", rather than (for example) throwing exceptions when not present; also indicated that the 2 streaming APIs should be present/absent together: it simplifies developer experience. 2017-05-24T04:50:58+00:00 Anne van Kesteren annevk@annevk.nl 2017-05-24T04:50:58+00:00 urn:sha1:d1a7ae0c6b38b72147812713890fa71a1db03611 This changes both WebAssembly.compile and WebAssembly.instantiate to be both more clear about response requirements and require an ok status. Fixes #1039. 2017-05-22T23:52:12+00:00 Brad Nelson flagxor@gmail.com 2017-05-22T23:52:12+00:00 urn:sha1:6cdc38bc079dad320c16c96d570d0fa1b13c97b7 2017-05-22T21:29:20+00:00 Derek Schuff dschuff@chromium.org 2017-05-22T21:29:20+00:00 urn:sha1:d1bd4a40119498feaee8ddb748207ab3f90ce702 Applies especially for use on the web, but useful for consistency in tools and other cases as well. 2017-05-18T18:37:39+00:00 Brad Nelson flagxor@gmail.com 2017-05-18T18:37:39+00:00 urn:sha1:89cfa6242fdc5f0f965e636bf0b927071ead356b Clarify how the source parameter is resolved. Clarify how the result of instantiate* is described. 2017-05-12T14:00:31+00:00 Mircea Trofin mtrofin@google.com 2017-05-12T14:00:31+00:00 urn:sha1:e330cb8d3c30ad4d1e2522b1b3ad5c829dd01c0d Proposing that we throw TypeError when the Response parameter has incorrect MIME type. This seems more in-line to what we do for: WebAssembly.{compile|instantiate}("hello!") 2017-04-04T23:27:18+00:00 Dan Gohman sunfish@mozilla.com 2017-04-04T23:27:18+00:00 urn:sha1:ef8db8fb41f20759b57d8a5a0c6ca44319c453fe