Chris Tate 9bdb36ed46 Report published values as frozen, sealed and not extensible ...

Under Node.js, publish() deep-freezes everything it reaches, so
Object.isFrozen and Object.isSealed return true and Object.isExtensible
returns false for a published object, array, Map or Set. Native builds
already refused writes into published values, but answered these queries
as for an unpublished value: publication marks an object immortal and sets
no frozen bit.

- record.isFrozen, array.isFrozen and the extensibility test of Maps and
  Sets also read an immortal rc word as published, the test of the
  published write guards, for the types the program may publish
  (PublishedTypes). Other types emit the code they did.
- scr_dyn_is_frozen, scr_dyn_is_sealed and scr_dyn_is_extensible answer
  for a published object, array, Map or Set, or a checked view of one,
  before materializing the view.

2026-10-27 12:57:41 -05:00

..

corpus

Report published values as frozen, sealed and not extensible

2026-10-27 12:57:41 -05:00

coverage-fixtures

Expect exact canonical mappings in the dynamic-slot coverage tests

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

deadstrip

…

diagnostics

Merge main

2026-10-26 06:51:26 -05:00

ffi

…

fixtures

Check with the shared tsc-ts server by default on Linux and macOS

2026-10-27 08:21:48 -05:00

harness

Convert number | undefined timer delays with ToNumber (#2427)

2026-10-27 12:42:02 -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

…

wasm-spec

…