Skip to content

Milestones

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 closed
  • Optimizing 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 closed
  • General bugs that need to be fixed more or less ASAP

    No due date
    6/12 issues closed
  • Uncommitted feature proposals; we hope by some version to adopt most of these ideas if they are proven

    No due date
    0/21 issues closed
  • The 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 closed
  • Every 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 closed
  • Things expected of a V1 release, but currently has obvious workarounds or isn't often expected

    No due date
    9/17 issues closed