Alex Rattray

I've been meaning to merge in @wcjohnson's fork (https://github.com/wcjohnson/lightscript) since he's done much more work on the language than I have, and his fork has several advantages. However, I'm not...

@wcjohnson I've made you an admin on the github.com/lightscript organization, so you should be able to overwrite the main repo, website, etc with your fork! Feel free to do so...

Interesting stuff! Real quick: 1) Would probably rather code-sharing be done with helper functions than merging/separating nodes... ideally, node visitors would contain only helper function calls, not manipulations directly. didn't...

Agreed this is an issue - thanks for reporting. I think a third resolution is possible: ``` function f(obj) { const { prop } = obj; return { prop };...

Cool, I hope to merge that in after `match`

My hunch is that `isArrowToken` in `eslint/lib/ast-types.js` needs to be expanded to include lsc arrows

Cool – although in the case of `now`, I'm actually going to revise the language itself to guide users more directly instead (shadowing with implicit `const` shouldn't be allowed, it's...

``` let someVar if someCond: someVar = 1 // SyntaxError: `someVar` is shadowed from a higher scope. If you want to reassign the variable, use `now someVar = ...`. If...

I saw this as well. Using curly braces instead of `:` for the class declaration dodges the bug too. Problem is it's looking for a closing `}` in the tokens...

nice, thanks for tracking all that down. relatedly, `MatchExpression`s currently have an `undefined` default-`else`, while `IfExpression`s have a `null` default-`else`. I *think* I want `match` to throw a runtime error...