xavi/nanowasm-design - Fork of https://github.com/WebAssembly/design/ with NanoWasm extensions.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fixup links to future features (#1157)	Joseph Richey	2017-11-15	1	-5/+8
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Remove dead link (#810)	wanderer	2017-05-11	1	-3/+1
\| \| \| \| \| \| \| \|	* Remove dead link * Added TODO * Remove TODO
*	Merge PostMVP into FutureFeatures for clarity. (#845)	Brad Nelson	2016-10-30	1	-3/+4
\|
*	Tagging future features with icon. (#839)	Brad Nelson	2016-10-27	1	-1/+3
\| \| \|	Added brief item on multiple return.
*	polyfilling update (#737)	Alon Zakai	2016-08-03	1	-3/+0
\|
*	Added a link to the FAQ to state why LLVM is chosen now	Jean Christophe Beyler	2015-12-11	1	-1/+1
\|
*	Drop references to LLVM repo	Luke Wagner	2015-06-16	1	-2/+2
\|
*	Use https links instead of http links for sites that support it.	Dan Gohman	2015-06-15	1	-2/+2
\|
*	Link to CAndC++.md from various places.	Dan Gohman	2015-06-12	1	-1/+2
\|
*	Moar fixes	JF Bastien	2015-06-12	1	-4/+4
\|
*	Fix capitalization correctly, per APA	JF Bastien	2015-06-12	1	-10/+10
\|
*	Fix sentence structure, and capitalize	JF Bastien	2015-06-12	1	-13/+13
\| \| \|	"Specify and implement incrementally" didn't quite make sense with the bullet points that followed. Rephrase.
*	Short document name bikeshed.	JF Bastien	2015-06-12	1	-2/+2
\|
*	Linkify 'mobile' and 'IoT'.	Dan Gohman	2015-06-10	1	-1/+2
\|
*	Remove the ™ from IoT.	Dan Gohman	2015-06-10	1	-1/+1
\| \| \| \| \| \|	This is meant to refer to the generic acronym [IoT](http://en.wikipedia.org/wiki/Internet_of_Things) rather than to make reference to any trademark.
*	Less buzzword, more compliance.	JF Bastien	2015-06-10	1	-1/+1
\|
*	Buzzword Compliant (TM).	JF Bastien	2015-06-10	1	-1/+1
\|
*	Internet all the Things	JF Bastien	2015-06-10	1	-1/+2
\|
*	Mention mobile platforms	JF Bastien	2015-06-10	1	-1/+1
\| \| \| \|	Mobile guides some of WebAssembly's concerns, but wasn't mentioned anywhere so far. This addresses #97.
*	Merge.	JF Bastien	2015-06-09	1	-3/+3
\|\
\| *	Fork out Web and NonWeb documents.	JF Bastien	2015-06-09	1	-3/+3
\| \|
* \|	Define portability	JF Bastien	2015-06-09	1	-3/+4
\|/ \| \| \|	Address issue #38.
*	Address sunfish's comments.	JF Bastien	2015-06-04	1	-2/+2
\|
*	Add a new feature test section, link to it.	JF Bastien	2015-06-04	1	-7/+7
\| \| \| \|	This is an initial skeleton. It's important to help people understand what we mean by feature test, and we've discussed it enough that I think we have a basic agreement of what we want to do, just not design of exactly how to do it.
*	Effective and efficient.	JF Bastien	2015-06-04	1	-2/+2
\|
*	Refactor polyfill quite a bit.	JF Bastien	2015-06-04	1	-1/+1
\|
*	Drop 'at high speeds', polyfill is already 'effective'.	JF Bastien	2015-06-04	1	-1/+1
\|
*	Merge, and drop the MVP change to asm.js. Discuss separately.	JF Bastien	2015-06-04	1	-8/+9
\|\
\| *	Rename "V1" aka "v.1" to "MVP".	Dan Gohman	2015-06-03	1	-7/+7
\| \|
* \|	Polyfill to JavaScript	JF Bastien	2015-06-03	1	-4/+3
\|/ \| \|	As [discussed](https://github.com/WebAssembly/spec/issues/96#issuecomment-108582323) asm.js is a smart implementation strategy to get polyfills to execute fast, but isn't a requirement. Some features aren't supported by asm.js, and a polyfill may decide to avoid asm.js on some browsers when performance isn't quite there.
*	Fix link	Luke Wagner	2015-05-18	1	-1/+1
\|
*	Tidy up HighLevelGoals even more	Dan Gohman	2015-05-18	1	-20/+26
\|
*	Capitalize "Web".	Dan Gohman	2015-05-18	1	-2/+2
\|
*	Tidy up HighLevelGoals	Luke Wagner	2015-05-08	1	-22/+20
\|
*	Update HighLevelGoals.md	Luke Wagner	2015-05-06	1	-3/+3
\|
*	mention polyfill limitations	Alon Zakai	2015-05-04	1	-2/+6
\|
*	Link HighLevelGoals.md to V1.md	Luke Wagner	2015-05-01	1	-1/+1
\|
*	wich	Luke Wagner	2015-05-01	1	-1/+1
\|
*	Move tooling link.	JF Bastien	2015-05-01	1	-0/+1
\|
*	Wording tweaks to HighLevelGoals.md	Luke Wagner	2015-04-30	1	-8/+6
\|
*	Update high-level goals, and add post-v1 features.	JF Bastien	2015-04-30	1	-10/+21
\|
*	Update HighLevelGoals.md	Luke Wagner	2015-04-29	1	-1/+1
\|
*	Create HighLevelGoals.md	Luke Wagner	2015-04-29	1	-0/+16
	This high-level design goal list has been passed around and generally agreed upon, so I'll put it up. Of course we can continue to discuss and iterate in issues.