Daniel X Moore

Also related `break label` inside of nested iteration iifes (contingent on our eventual label support).

We can currently do something similar with: ``` x = {} (x.'hello world' ?= []).2 = 3 ``` I'm not convinced that an additional specialized syntax is worth it in...

Currently: ```coffee ( ( x.arr ?= [] )[1] ?= {} ).y = 9 ``` It may make sense to try something like this for a possible future syntax: ```coffee x.arr?=[][1]?={}.y...

Now that we have pipes: ```civet x |> .foo ?= [] |> .append 5 x |> .foo ?= {} |> &[key] ?= [] |> .push value ``` ```typescript (x.foo ??=...

It's not the specific error, just that the link doesn't navigate in VSCode.

TS is able to keep track of the type information: https://www.typescriptlang.org/play?experimentalDecorators=true#code/DYUwLgBATiBmDcAoRBLWEAUiKZugvBACYD2AxgK4C2IAdmAHQCOFIUAngMoihlglQMAIgDEAZxI0wACxS0A5kICUSxEogBvbBDIlaYyDxA16EQniQ4jJxgEMADvbpEAwrOBEMADyVIAvkA Do you have a more specific example?

What about: ```typescript array[#?] // array.length > 0 // indexing out of array bounds can cause perf deoptimizations array[?] // let l = array.length; l ? array[Math.floor(Math.random() * l)] :...

What about `#` as a general shorthand for `.length` anywhere? That way it will work with strings, arrays, and anything else. It also plays nicely with `arary#

I think having `#` be the length of the object to the left of the current enclosing `[` is just magical enough ✨ It might not get in in the...

Now that we have precedence and associativity we can adjust the parser to have more things be binary operators but it may not be a small task.