Daniel X Moore

As a workaround you can do this: ```civet 'civet coffeeCompat' class Foo get [Symbol.toStringTag]() 'Foo' console.log Foo::[Symbol.toStringTag] ```

Some relevant Python references: - https://stackoverflow.com/a/23748240/68210 - https://youtu.be/OSGv2VnC0go?t=950 I'm a fan of the capability but I'd like to find a better way to name it. The Python `for ... else`...

Looks like this works now with the recent changes: https://civet.dev/playground?code=dW5kbyA6PSA9PiBlbmdpbmUgPSBFbmdpbmUuZnJvbUpTT04ganNvbiBpZiBqc29uPyA6PSBoaXN0b3J5LnBvcCgpCg%3D%3D

It looks like we'll need to do these manually. 😿 https://github.com/tc39/proposal-destructuring-private

I think we would instead do something like: ```javascript ret.#x = this.#x, ret.#y = this.#y; ``` Essentially pollyfilling without destructuring ourselves. We may need to consider what to do if...

Neat idea! Some random thoughts: - Operator overloading is something we'd like in the future. Maybe `"skeleton blank house cipher car"|" "` -> `"skeleton blank house cipher car".split(" ")`. We...

For `class` and multiple of the same keys we should have some way of aliasing but I'm not sure of the best syntax for it yet.

This is something we want to support eventually. I think the overall fix will be to convert the expressions to actual blocks that execute before the assignment. Wrapping in an...

We should match TC39 on this. ``` f = (x) -> y := do await x ``` A better transpilation for us would be something like: ```typescript f = async...

There's not currently any way to fallthrough using Civet's pattern matching. You can fall through using the JS style `switch` and `case` clauses but they won't be able to mix...