Felix Roos

> Sorry I was assuming a in the above, but where . has higher precedence than >>, so the mul here is local: "." has higher precedence. Just checked with...

> We're not completely free to nest stuff with method chaining, as this won't work: `freq(220).(cutoff(2000).mul(2))` Why not just ```js freq(220).cutoff("2000".mul(2)) ```

unfortunately, using dots this way wont work with js. we could still add union for such cases. but i wonder if you even need parens for union, because they say...

> Ah right, so I'd need more parenthesis.. ```js freq("220(5,8)") . ((cutoff(sine.range(200,400)) . room(saw) ).every(3, fast(2))) ``` So this example is implying we want the `every` to run on the...

okay so I kind of lost track of the common thread, but I think we should be alright with union approach `a`.. > It feels better without the space though...

clearly it should

blocked by https://github.com/shapesecurity/shift-parser-js/issues/452

wont fix, as #249 works with skypack

I wonder if the assumption of 1 cycle / second has any disadvantage? If not, we could implement cps like cpm

But anything against implementing it with slow, assuming a hard coded cps? I kind of like 1s because it's normalized