Ron Buckton

> Q: Is it possible for us to help enforce monomorphic object shapes using a lint rule of some kind? We basically want to enforce that we don't potentially add...

> I'm curious. How I can run the perf on my own project? The tool we use for benchmarking isn't public, but it essentially just runs `tsc --extendedDiagnostics` repeatedly on...

I don't know that we've ever supported inference to two rest elements of a tuple that has one or more fixed elements between them. What ends up happening is that...

This is unfortunately a design limitation as we have a very narrow heuristic that provides rudimentary support for inferring to multiple rest types in a tuple. It's not clear at...

We discussed this in a design meeting recently. Even though the proposal makes an exception for registered symbols from `Symbol.for`, we don't want to take on the complexity to model...

The solution we use for `ArrayBuffer | SharedArrayBuffer` in typed array constructors is the same as your proposed solution with `AllowableWeakTypesStore`, so I would recommend that approach. I'd recommend a...

@acutmore, @leoelm: Is bloomberg/TypeScript#76 ready for a PR? It looks pretty much like what I would have written given my earlier suggestion.

> * if this particular test case would work if "the second request" would be performed conditionally (in other words - is "the first request" returning anything here?) > 1....

I'm updating the PR, but it may have been broken by some of the changes in #53996 as it's no longer giving the expected results. I'm working out what the...

This issue appears to be that we no longer skip type argument inference from arguments when checking for string literal completions, and end up inferring `never` from an argument instead...