List view
- No due date•0/5 issues closed
Automated tests, or projects to make to test for bugs and/or feature usability.
No due date•0/2 issues closedOptimizing compiler performance or (more likely) generated code speed & size. Optimizations are cool and its never too early to optimize, but also doesn't help us along in the iterative design process of Wake, so we should prefer making core features and solving usability bugs.
No due date•0/3 issues closedGeneral bugs that need to be fixed more or less ASAP
No due date•6/12 issues closedUncommitted feature proposals; we hope by some version to adopt most of these ideas if they are proven
No due date•0/21 issues closedThe goal is to have js interoperability by the end of this milestone -- calling js from within wake, calling wake from within js.
No due date•8/25 issues closedEvery large feature we want by V1 should go in here, unless having/not having the feature is easy and if not having the feature inhibits normal program writing.
No due date•16/36 issues closedThings expected of a V1 release, but currently has obvious workarounds or isn't often expected
No due date•9/17 issues closed