Asking the bridge's checker for the type of an empty array literal that is contextually typed as the empty tuple triggers Go panic

andreww2012

The minimal code that causes a process crash when `@typescript-eslint/no-unsafe-return` ESLint rule is being run on it: ```ts export const empty: [] = []; ``` Example of error: ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x2 addr=0xf8] checker.(*Type).ThisType(...) internal/checker/types.go:754 api.newTypeResponse(...) internal/api/proto.go:1130 api.(*snapshotData).newTypeResponse(…) internal/api/session.go:455 api.(*Session).handleGetTypeAtLocation(…) internal/api/session.go:2844 ``` Related problem: https://github.com/johnsoncodehk/typescript-native-bridge/issues/17 The full minimal reproduction (AI written): https://github.com/andreww2012/repros/tree/main/typescript-native-bridge-empty-tuple-this-type-panic