Destructuring assignment with computed property name does not help narrow types as intended.

Nobody has claimed this yet.

### 🔎 Search Terms

"destructuring assignment", "computed property name", "type narrowing"

### 🕗 Version & Regression Information

Happen to all existing version in typescript playground.

### ⏯ Playground Link

https://tsplay.dev/w1eElw

### 💻 Code

```ts
declare let obj: Record

declare let cond: boolean;
declare let key: string;
let result: string | null = null;

if (cond) {
({ [key]: result } = obj);
result;
// ^?
}

if (cond) {
({ 'key': result } = obj);
result;
// ^?
}
```

### 🙁 Actual behavior

Type narrowing did not happen to the assignee variable `result` after the assignment `({ [key]: result } = obj);`.

### 🙂 Expected behavior

Expecting the assignment `({ [key]: result } = obj);` will narrow the assignee variable `result` to non-null.

### Additional information about the issue

_No response_

Start with the linked TypeScript Playground reproduction and compare the inferred type of result after the computed-property destructuring assignment and the literal-property assignment. Trace the type-narrowing behavior involved and verify that the completed change preserves the expected non-null narrowing in both examples.

Written by the indexing model from the issue text.