Daniel X Moore

For code generation of the `let a = a` where a is in the outer scope it could go something like: ```coffee a = 1 b = (x) -> let...

I think we can fix this by proxying `window.opener`

This can all be done pretty easily through the Github ui, so it's not a real priority.

Probably depends on #35

We can start with a simple utility component that searches source files for strings and returns an array of results. This will allow some simple yet helpful things like "which...

A possible refinement/expansion could be `?>` and `!>` as pipe-if and pipe-unless. ``` foo := try line1() !> return bar := try line2() !> return ... vvv let ref; try(){ref...

This seems to be a little tricky to unify with object notation since: `{ s: t } from ./stuff` makes sense as `s as t` but: `export { s: t...

Related #1280

Related to https://github.com/DanielXMoore/Civet/discussions/1081

CoffeeScript's solution is to raise a parse error but I think we can do better. ```javascript const returnSymbol = Symbol("return") const compiled = (() => { try { return {[returnSymbol]:...