bbrk24
bbrk24
I'm now experiencing a limited form of this that only complains about new properties:   This project's tsconfig, for reference: ```json { "compilerOptions": { "strict": true, "lib": ["ES2023", "ESNext.Regexp"],...
Some more information I realized this morning: Even though it usually only affects core JS types like `Array` and `Error`, not DOM APIs, this only ever happens to its fullest...
As best as I can tell, this is no longer an issue in extension version 0.3.21.
Just ran into this in a different context: ```coffee return false unless (and) ... ```
A couple notes: - If the pipe counts as an operator (which it might not — see #1050), this supersedes #897. - If assignment operators are included in this, the...
`...` in object literals doesn't seem terribly useful: 
`.` does not currently work in constructors (e.g. `x |> new Foo ., y`).
> Perhaps we also want `#?` to mean `.length > 0`, so that we can easily convert lengths to booleans? As much as this would be nice to have, it...
I see. The error message is more informative if I type `same(▷)` instead.
The TC39 proposal says `|>` is on the same precedence level as `=`, but `same(=)` also doesn't work for much more obvious reasons. Though I am a little surprised `same(++=)`...