bbrk24
bbrk24
You're right; I just checked, and the compilation has not changed since then.
I think it's different. That issue can plausibly be fixed by removing a newline from the generated code, and emitting `for (const key in obj){const value = obj[key];`. This issue...
> It would be nice if this worked, but `|>` currently can't follow a loop like this: > > ```js > t = for i of [1..3] > Math.sqrt i...
I agree. If it really can't be done with a simple `as`, you can always use `as!` or `as any`.
https://github.com/bbrk24/mariokart-optimizer is where this is happening to me
This also causes a more severe version of #825 -- `document.que` autocompletes to `document.this.querySelector`.
In the past, DOM APIs would still have the correct types and tooltips (or, as correct as they could be without arrays). However, today I got this: 
Saving a file isn't the only trigger. If "jump to definition" opens one of the built-in lib.\*.d.ts files, that can also trigger this.
Simply having a lib.\*.d.ts file open in another tab and performing an edit can trigger this. This is ridiculous.
Here's the Language Server output, if that helps. It doesn't seem to suggest anything out of the ordinary: Civet LSP Output Init /home/bbrk24/workspace/NewSolitaire/ open file:///home/bbrk24/workspace/NewSolitaire/src/index.civet onDidChangeContent file:///home/bbrk24/workspace/NewSolitaire/src/index.civet Spawning language server...