Repository navigation
fix: open built-in chains on reads by unproven keys; no IIFE parameter binding for self-referencing named functions - #468
Merged
Merged
Conversation
Sorte1
force-pushed
the
fix/rx11-proto-reach
branch
from
November 20, 2026 23:40
28c6c52 to
c2533cc
Compare
…d no parameter of a self-referencing named function from its call A computed read, a computed pattern key or a .get call whose key is not proven numeric, enumerated or a resolved name other than __proto__, prototype and constructor now counts as obtaining a built-in prototype. This also feeds the cross-input built-in scan, so an input that patches a prototype through such a key stops folds in the other inputs. A function expression called in place binds its parameters to the call's arguments only when its own name is never referenced.
…umber earlier in the same function body
…rs from direct calls
… prove keys from unset numeric variables A read whose value is only tested, compared, coerced while the relied built-ins are intact, or called with the result dropped cannot hand out a prototype. The notes test decoder now shifts its index like the obfuscator.io decoder it stands for.
…ved key in another input
…es with the unresolved-key chain reads
Sorte1
force-pushed
the
fix/rx11-proto-reach
branch
from
November 20, 2026 23:46
c2533cc to
d25acae
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the two CRITICAL default-lane findings of review/r6-a25rr9.md and finding 2 of review/r6-ml7.md.
.get(o, k)call whose key is not proven safe now opens the built-in chains when its value is kept. A key is safe when it is numeric, enumerated, a resolved name other than__proto__/prototype/constructor, a parameter overwritten with a number earlier in the same body, a parameter that only receives safe keys from direct calls, or an unset variable written only with numbers. Reads that are only tested, compared, coerced (relied built-ins intact) or called with the result dropped do not count. The same walk feeds the cross-input scan, so a prototype patched through such a key in one input stops folds in the others.Rows: crates/untwist/tests/data/rename_a25rr (rx11-, q-rx11-). r5 fin/t1-t32, m2/m3, m2/m4 and all r6 a/b/c rows match node under no flags,
--rename smart,--rename mangle;--unsafedifferences are only the prototype-patch rows inside its premise. r6-ml7 n4/n6: 0 default-lane differences.Gates: full sweep 0 worse in either lane, Krunker and game.js byte-identical in both lanes and with both renames, BASELINEs unchanged, wasm 16,468,378 bytes, local untwist-ci green.