`strictNullChecks` short-circuits the subsequent type checks

Bug Report

hello， I encounter a strange bug when I use strictNullChecks: true, and here is an example:

interface A {
  a: number;
}
const list: A[] = [];
list[0] ??= {};  // throw an error: Property 'a' is missing in type '{}' but required in type 'A'
list[0] = list[0] ?? {};  // the type checking not work !
list[0] = list[0] || {};  // the type checking not work !

🔎 Search Terms

🕗 Version & Regression Information

• This is the behavior in every version I tried

⏯ Playground Link

It seems the type checking works after I close the strictNullChecks options
Playground link with relevant code

💻 Code

interface A {
  a: number;
}
const list: A[] = [];
list[0] ??= {};  // throw an error: Property 'a' is missing in type '{}' but required in type 'A'
list[0] = list[0] ?? {};  // the type checking not work !
list[0] = list[0] || {};  // the type checking not work !

🙁 Actual behavior

list[0] = list[0] ?? {}; doens't throw any errors

🙂 Expected behavior

I expect that list[0] = list[0] ?? {}; should throw an error

Commencez par le TypeScript Playground lié et reproduisez l’exemple avec strictNullChecks activé, en comparant ??= aux affectations ?? et || qui suivent. Suivez le chemin de vérification des types pour ces formes d’affectation et ajoutez ou mettez à jour un test de régression montrant que l’affectation d’un objet incomplet signale l’erreur de propriété manquante.