Daniel X Moore

I'm rereading this and am in favor of adding back-calls largely compatible with LiveScript. One change: instead of `_` for the argument placeholder we'll use Civet's `.` so we don't...

The `lhs` can also be multiple comma separated function arguments so I think it's actually an arguments list with implicit parentheses. This should also cover the zero item list as...

> Is the constructed function a `->` (`function`) or `=>` function? Your code example uses `->` but later on you say it should be `=>`. I imagine `=>` is the...

We may also be able to convert `is in [...]` with range literals into comparison operations.

I have mixed feelings about this one... I think it could be handy to lift above trailing call expressions much lifting above. It's easy enough to short circuit the chain...

Thanks for the explanation, I'm mostly convinced, however there is one other situation I think needs to be considered: ``` // Currently .normalize() is applied inside the wrapper y :=...

> * `&` lifts to _just inside_ the nearest function call, assignment, pipeline, `return`, or `yield` > * `.` lifts to _outside_ the nearest function call, **and from there, lifts...

The delayed arguments seem to work ok already with this construct: ``` (setTimeout ., 100) => console.log(x) ``` The way I think about `.` is less about currying / managing...

Good point, maybe we should continue through parentheses. I can see it coming up in math equations pretty regularly.

We could probably make a bash script that automates the update.