Jake Bailey

https://github.com/microsoft/typescript-go/blob/bd7c18dc8ed3c5ed960d72f1e329353f0a594bcc/internal/fourslash/tests/gen/autoImportCrossProject_symlinks_toSrc_test.go or similar, the tests I skipped when I added auto import fixes

Hm, this ended up failing all of the tests.

Seems like three tests are being fixed: ``` internal/fourslash/_scripts/failingTests.txt | 3 --- internal/fourslash/tests/gen/autoImportPnpm_test.go | 2 +- internal/fourslash/tests/gen/autoImportSymlinkCaseSensitive_test.go | 2 +- internal/fourslash/tests/gen/importNameCodeFix_pnpm1_test.go | 2 +- ``` And linting needs to be...

Do we know in general how much faster this is compared to the more naive but simple approach? I was kind of hoping we could get away with "caching within...

> Now, with go to definition, I don't think it's that big of a difference. However, we are going to soon add support for source mapping to find all references,...

> Go to definition I don't think will be a problem, which is why I mentioned FAR, but maybe even that is not really a problem If we are caching...

I don't think this is enough information for us to investigate. Do you have the code?

You'll probably need to start deleting code out of your project until you find the code that's breaking things.

@ahejlsberg you self assigned this, not sure if you saw https://github.com/microsoft/typescript-go/pull/2221#issuecomment-3613919781 but we are dumping method overloads into the source file for these object method overloads, and I am not...

We would need the actual repo to check, but you could use `--pprofDir` to collect profiles of how it's currently behaving.