Jake Bailey
Jake Bailey
This is a challenge in the Go code since we don't have two kinds of null anymore; I think we should have some sort of "unresolved" compiler options we use...
Note that tsconfig parsing operates on SourceFiles, so never actually interacts with Go's json package. This is all stuff we'd need to implement ourselves differently.
Is there any chance you could get an LSP message log from the output window, or at least the end of it (sanitized) when this happens?
@typescript-bot perf test this
@typescript-bot perf test this
Half a gig of memory for vscode is a bit scary, though, given how close that is to the max memory limit...
@typescript-bot perf test this
Much better, though emit is now much slower on certain benchmarks. Maybe a case or two aren't monomorphic for those benchmarks?
@typescript-bot perf test this
@typescript-bot perf test this faster [email protected]