Prevent contextual typing recursion in destructuring initializers

[Copilot]

The checker could recurse infinitely when contextual-typing an object literal initializer for a destructuring with an annotated union (string | number | symbol), leading to a stack overflow on patterns like const { c, f }: string | number | symbol = { c: 0, f };.

Description

• Track the active binding pattern while computing an initializer’s type so contextual typing doesn’t re-enter the same pattern; references inside that pattern now yield a non-inferrable any instead of recursing.
• Added regression test destructuringContextualBindingStackOverflow.ts with baselines to cover self-referential destructuring scenarios, including { c, f }, { a, f: (1 + f) }, and cross-referenced { a: f, f: a }.

Testing

• npx hereby runtests --tests=tests/cases/compiler/destructuringContextualBindingStackOverflow.ts
• npx hereby runtests-parallel
• npx hereby lint
• npx hereby format

Original prompt

Fix the stack overflow that occurs when checking this code:

const { c, f }: string | number | symbol = { c: 0, f };

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[RyanCavanaugh]

@copilot add testcases

const { a, f }: string | number = { a: 0, f: (1 + f) };

and

const { a, f }: string | number = { a: f, f: a };

[Copilot]

@copilot add testcases

...

Added both cases to the regression test file (commit 0392f4f).