Malte UblandClaude Opus 5.5 a4a84f59da Resolve a promise-or-unit operand in Promise.resolve ...

`Promise.resolve(p)` over `Promise<void> | void` — an async callback's
declared result — was refused: the maybe-promise detection required
every non-promise arm to carry a value, while a nullish arm is exactly
what `Promise.resolve` fulfills as undefined. `promiseOrUnitUnionOf`
names that shape, and the resolution reuses the existing adopt-or-
fulfill path, so the promise arm passes through unchanged
(`Promise.resolve(p) === p`).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-28 05:37:50 -07:00

..

corpus

Resolve a promise-or-unit operand in Promise.resolve

2026-10-28 05:37:50 -07:00

coverage-fixtures

Expect exact canonical mappings in the dynamic-slot coverage tests

2026-10-27 07:42:33 -07:00

deadstrip

…

diagnostics

Capture stack traces with Error.captureStackTrace as Node does (#1809)

2026-10-27 13:49:06 -05:00

ffi

…

fixtures

Merge main

2026-10-27 16:45:14 -05:00

harness

Convert more structural values: class views, promise arms, index-signature records, tuple unions (#2442)

2026-10-27 21:29:07 -05:00

library-mode

Add object literal members through the store caches in untyped code

2026-10-25 08:24:12 -05:00

node-parallel

…

test262

Convert compareArray's message only when the arrays differ

2026-10-24 16:16:23 -05:00

wasm-spec

…