`.then(onresolved)`'s return type should not be inferred from contextual type

lib Update Request

Configuration Check

My compilation target is ES2015 and my lib is the default.

Also reproducible with target ESNext, ES2022 ect.

Missing / Incorrect Definition

Promise.prototype.then

Sample Code

TypeScript infers the return type of then from the contextual type information when called with only one argument.
This can cause unexpected results

let a: string | undefined
const b = a ?? await somePromise.then(() => "str")

I expect b to be string because either a is a string, somePromise resolves and then returns a string, or somePromise rejects and await throws so b is not assigned.
However b is actually string | undefined because the contextual type on the RHS of a nullish operator is the type of the LHS
and then inferred it's return type from the context because TResult2 was not inferred from arguments.

b satisfies string | undefined

• playground

I think there's actually two issues here

• The contextual type of the RHS of nullish operator is the type of the LHS
• .then's type definition does not use overloads for different number of arguments

The first issue seems debatable, I can understand the current behavior but these alternates make sense as well

1. The contextual type of R should be unknown or the same as the whole L ?? R expression
2. The contextual type of R should be NonNullable<L>

Let me know if this should be a separate issue or if there is interesting reading on the current behavior.

The next issue is caused because the return type of .then is Promise<TResult1 | TResult2> and TResult2 is not inferred from then's arguments when onrejected is not provided so it's inferred from the contextual type.

I think this issue can be fixed by changing the library to use overrides

then<TResult1>(onresolved: (t: T) => TResult1): Promise<TResult1>
then<TResult1, TResult2>(onresolved: (t: T) => TResult1, onrejected: (err: any) => TResult2): Promise<TResult1 | TResult2>
// more overrides for 0 or only onrejected args.

Documentation Link

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/then
https://github.com/microsoft/TypeScript/blob/main/src/lib/es5.d.ts#L1524

Beginnen Sie mit der Definition von Promise.prototype.then in src/lib/es5.d.ts ungefähr bei Zeile 1524 und reproduzieren Sie das bereitgestellte Playground-Beispiel. Prüfen Sie, wie die Formen mit einem und mit zwei Argumenten typisiert sind, und bestimmen Sie, ob das Problem der kontextuellen Typisierung des nullish-operator separat behandelt werden sollte. Als erledigt gilt die Aufgabe, wenn der beabsichtigte Typ der Form mit einem Argument verifiziert ist, ohne das dokumentierte Promise-Verhalten zu beeinträchtigen.