aboutsummaryrefslogtreecommitdiff
path: root/FeatureTest.md
Commit message (Collapse)AuthorAgeFilesLines
* Fixup links to future features (#1157)Joseph Richey2017-11-151-2/+2
| | | | | | | | | | | | | | | | | | 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.
* fix the messed up SIMD link (#988)Sakthipriyan Vairamani2017-02-141-1/+1
|
* Merge PostMVP into FutureFeatures for clarity. (#845)Brad Nelson2016-10-301-5/+6
|
* Tagging future features with icon. (#839)Brad Nelson2016-10-271-6/+13
| | | Added brief item on multiple return.
* fix improperly spaced markdown blocks and typos (for formatting on website ↵Seth Thompson2016-10-261-0/+4
| | | | (#837)
* Add JS Memory and Table API, support dynamic linking (#682)Luke Wagner2016-06-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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
* Fix feature testingJF Bastien2016-03-181-4/+7
| | | | | | It was removed in #523, but was still referenced. Leave it as a high-level sketch for now. Fixes #613.
* Remove more references to `comma` and `conditional`.Dan Gohman2016-01-281-1/+1
|
* Merge pull request #418 from mtrofin/patch-2JF Bastien2015-10-271-0/+2
|\ | | | | Capture of scenarios motivating feature testing.
| * Update FeatureTest.mdMircea Trofin2015-10-261-14/+1
| |
| * Back to pronouns.Mircea Trofin2015-10-221-6/+6
| |
| * Incorporated feedback.Mircea Trofin2015-10-211-7/+7
| | | | | | | | - link to PostMVP.md - replaced pronouns with giving the user a name in each scenario, and then using the appropriate pronoun. This makes cross-referencing scenarios easier, too.
| * Separate scenarios motivating feature testingMircea Trofin2015-10-211-0/+15
| | | | | | | | | | Moved a few of the already described scenarios, trying to isolate the motivating problem from possible solutions. Added a development time scenario and one for restrictive target environment.
* | Replace `operation` with `operator`titzer2015-10-231-2/+2
|/
* JS -> JavaScriptLuke Wagner2015-10-151-1/+2
|
* Fix wording, add linkLuke Wagner2015-10-151-4/+6
|
* Move code example out of bullet b/c markdown diesLuke Wagner2015-10-151-23/+27
|
* Add SIMD example and more details according to commentsLuke Wagner2015-10-151-7/+42
|
* Provide more details in FeatureTest.mdLuke Wagner2015-10-151-7/+45
|
* Add feature test AST nodeLuke Wagner2015-09-101-4/+4
|
* Update URLs to account for spec->design repo renamingLuke Wagner2015-06-101-1/+1
|
* Address sunfish's comments.JF Bastien2015-06-041-1/+1
|
* Add a new feature test section, link to it.JF Bastien2015-06-041-0/+11
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.