Daniel X Moore

@CherphAlt Have you looked at https://github.com/DanielXMoore/Civet/tree/main/integration/unplugin/examples/astro which was recently added?

Since `template` would expand the list of reserved words we may be able to do something like `function! id(v) ...` This reinforces the concept that it's an inlined function and...

Adding `not` at the same precedence as `!` is good and should be done. Having different precedence like perl is an interesting experiment that I think could have value but...

Having an alternative `tsconfig.json` that Civet detects and TS doesn't is a good idea! That way I won't have to keep enabling and disabling extensions per workspace. I'll try to...

Spreads could also apply to object results as well.

I've submitted a fix to node https://github.com/nodejs/node/pull/49461 You could build a patched version or wait a couple years for them to merge and release it.

I agree that we should match the CS2 behavior when in `coffee-compat` mode. For migrating to Civet/ES semantics I would recommend pulling out the `=` field assignments as `:=` outside...

It would be slightly difficult to add compile time checking since it's valid ES (accessing a global variable inside the method body). Currently opening the file in VSCode with the...

Currently `coffeeCompat` is implemented as a meta flag that enables a collection of more specific options. Adding `"civet coffeeCompat -coffeeCrazyClassAttrs"` would have all the other coffee compat items but omit...

I finally realized what CS2 means by [class definitions are blocks of executable code](https://coffeescript.org/#classes) [CoffeeScript 2](https://coffeescript.org/#try:class%20API%0A%20%20x%20%3D%20-%3E%205%0A%0A%20%20cool%3A%20x%0A%0A%20%20%7Ba%3A%20b%7D%0A%20%20%0A%20%20do%20-%3E%0A%20%20%20%20yolo%0A%0A%20%20while%20x%20%3E%201%0A%20%20%20%20x--%0A%0A%20%20HTTP_GET%20%3D%20'GET'%0A%20%20HTTP_HEAD%20%3D%20'HEAD'%0A%20%20HTTP_VERBS%20%3D%20%5BHTTP_GET%2C%20HTTP_HEAD%5D%0A%20%20x%20%2B%3D%203%0A%20%20%0A%20%20callApi%3A%20-%3E%0A%20%20%20%20console.log%20HTTP_VERBS%5B0%5D%0A) I don't think that makes implementing this any harder, it just clarifies the scope...