3 ms·
Looks interesting. The section on "Optional Typing" is too brief. Type inference is mentioned, but there are no details on how the type system functions and wh
by noelwelsh 13y ago
Looks interesting.
The section on "Optional Typing" is too brief. Type inference is mentioned, but there are no details on how the type system functions and what a failure of type checking means. It seems one can't name types, which is odd and will lead to a great deal of repetition.
- cameronkknight 13y agoTypes are allowed to be any of the primitive types (e.g. Boolean, Number, etc.), null, undefined, any custom "class", a specifically-typed array (e.g. [Number] for an array of numbers), or a specifically-typed object (e.g. {x: Number, y: String}). I do plan on being able to alias the typed object as an "interface", just haven't gotten around to that. A failure of type checking generally means you get an early runtime error, though I plan on reworking things to catch more at compile-time (while still not being a pain).
- tel 13y agoHow do types work with objects and classes? Can you subtype?
- cameronkknight 13y agoYeah, class Child extends Parent