1. There's a compiler validation phase, it guess types from definitions and assi...

ulisesrmzroche · on March 9, 2014

Does this depend on using --harmony? Or are you faking the generators?

lucio · on March 9, 2014

today it depends on --harmony (only for "yield"), but it is trivial to add an option to use node-fibers instead (same functionality of ES6-generators for node>=v0.8).

See https://github.com/luciotato/waitfor ,node-fibers, and the same with generators: https://github.com/luciotato/waitfor-ES6

ulisesrmzroche · on March 14, 2014

It's good that it's not faking generators though, stick with harmony. Fakes slow to a crawl after a while.

peq · on March 9, 2014

How does the type guessing and the type system in general work?

lucio · on March 9, 2014

1. Type guessing:

- if you have a "class Token" and later do "var token", the type is guessed by name affinity.

- if you do:

    token = .getToken()
    other = token

the type of "other" is guessed from assignment (:Token)

2. Type annotations: you directly state type

          var other:Token
          var read: Token array

The compiler does a "pseudo-execution" of the AST, guessing types and validating property access.