サンプル

Prove Object3D.traverse traversal semantics in three 0.185.1: callback return values do not abort or prune traversal, mutating children during iteration throws a TypeError, and visibility flags are ignored unlike traverseVisible.

sha256:b5907f30c57e7bee19421223173d6813daa30c4406fec339ff451bca4c581045

MIT-0

実行証拠

宣言環境と署名済み検証実行を分け、証明範囲を明確にします。

宣言された環境 node linux x64 node node npm

環境	コントラクト	ステージ	実行日
node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9	PASS	compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1	2026-08-19
node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1	PASS	compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1	2026-08-19

HOW

ゴール: Prove Object3D.traverse traversal semantics in three 0.185.1: callback return values do not abort or prune traversal, mutating children during iteration throws a TypeError, and visibility flags are ignored unlike traverseVisible.
パッケージ: three 0.185.1
シンボル: Object3D.traverse
環境: node
作成日: 2026-08-19T13:09:41Z

Object3D.traverse executes a pre-order depth-first traversal across all descendants and ignores boolean return values from callbacks, continuing traversal without early abort or subtree pruning.
Object3D.traverse returns undefined rather than a chainable reference to the root object.
Object3D.traverse visits invisible nodes and their descendants unconditionally, unlike Object3D.traverseVisible which terminates descent at invisible nodes.
Removing a child object during Object3D.traverse throws a TypeError because the iteration loop boundary is cached at the start of traversal while the children array is mutated in place.
Object3D.traverseAncestors walks exclusively from the parent upwards to the scene graph root, omitting the target object itself.