Ron Buckton

In my original post above, I explicitly call out block scope as I definitely would not want a cover grammar for block vs object literal. Especially since such a cover...

I just installed v0.7.7 and I'm seeing syntax highlighting issues in a standard gcode file when there is a string of text for a command like M117 or M0: ...

IIRC, the class element ordering just mirrors the order in which class elements are defined, which maintains lexical ordering _within a group_, where the groups and order are: 1. static...

Option 3 is not really viable, because it falls apart even without modules: ```js function deco() { f(); } @deco function f() {} ``` If we did go with Option...

@hax, classes have a TDZ and the declaration isn't yet initialized when the decorator is called, so you would get a runtime error. This is not the case with functions.

@Alphare, my suggestion for lazy decorator evaluation was to have the decorator applied the first time the decorated function is _accessed_, not the first time it is called. Unfortunately, this...

I was just discussing parameter decorators with @littledan, and wanted to capture some of my notes here for the inevitable parameter decorators proposal. Parameter decorators are extremely valuable for a...

Extractors are not the correct feature to build runtime types on. While you can use extractors for runtime assertions, their purpose is to augment destructuring. IMO, a better feature upon...

> We could also get a lot of the type-checking power of this by having a default matcher implementation that relied on an `instanceof` check (which is already customizable via...

> I don't understand how `@@hasInstance` "does not work across realms", but that's perhaps not really relevant. More specifically, the default implementation of `@@hasInstance`/`instanceof` does not work for built-ins for...