Gabriela Araujo Britto

@typescript-bot test it

@Andarist this probably needs a merge from main to update the baselines before I merge.

@typescript-bot pack this

I thought about this some more, and I think I'm still a little confused about some things in our definition of "unused" for the purposes of `noUnusedLocals`. Should `Bar` and...

But doesn't this PR mark `Bar` and `foo` as used vs not used in current version? https://www.staging-typescript.org/play?noUnusedLocals=true&module=1&ts=5.5.0-pr-57649-11#code/KYDwDg9gTgLgBAbwL4G4CwAoTBjANgQwGdC4AhfKRTOGuAW2BgAsIATACgEoqNa+5sEAHaF4eEgF4BBYnABiECD34q4o-DACW2Zar2CR8AJ5wp5KOl57VBwhFzAAdLggBzdkc6XrtJNVV+VipQjACuUELShN6+mIGYAGahQthawnAJily6NLZiuJLSRCQKSgj+KupaOuVB1nlwJlKZEDE+tvZOLu6ebfyBfAO0ITDhkeKWSEA

I'm going to close this because the source package does seem to have a named `ReCAPTCHA` export, and there's been no activity on this PR. Feel free to re-open if...

Update on this bug: I've looked into making type checking array literals faster, but it doesn't look like this would be enough to solve the intellisense slowdown for the examples...

> because a fresh build does still take about 2.7x longer than main today does What's the impact on an editor scenario? Say, editing `checker.ts`. It's already pretty bad today...

Investigating the minimal repro posted here, it doesn't seem like this is a bug. What happens is that, when we try to compute the type of `property.compute` on line 6,...

> hi @gabritto > > thanks for the explanation. Following the thread as we have a similar issue > > do you know why this could have appeared with typescript...