Chris Tate fd768cd914 Initialize import cycles that re-export a member with export * ...

An `export * from` declaration binds each re-exported name to the binding
of the module that declares it, like a named re-export, so it has no
initialization state of its own. Import cycles whose modules re-export
another member of the cycle this way now compile with the exact cycle
initialization: re-exported names read the same values, and throw the
same temporal dead zone errors, as in Node. `export * as ns` of a cycle
member keeps the SC1016 refusal.

pi-coding-agent's sdk.js (sdk.js → agent-session-runtime.js →
agent-session-services.js → sdk.js) has this shape.

Refs #1777.

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

..

corpus

Initialize import cycles that re-export a member with export *

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

coverage-fixtures

Merge main

2026-10-23 05:57:14 -05:00

deadstrip

…

diagnostics

Compile unions of typed-array classes (#2011)

2026-10-23 20:00:12 -05:00

ffi

…

fixtures

Inspect dynamic classes, functions and %o arguments as Node does (#1848)

2026-10-23 23:23:51 -05:00

harness

Initialize import cycles that re-export a member with export *

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

library-mode

Revert "Cache untyped property access in programs that declare classes (reland)"

2026-10-23 15:53:36 -05:00

test262

Run Test262 tests that include testTypedArray.js

2026-10-23 14:27:20 -05:00

wasm-spec

…