object model step 1: narrow the Object.create family census (freeze/relink/unnamed define) to reachable targets
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript, rust
- Domain
- compilers
Research direction
The payload names no source files, so start by finding the census of freeze, seal, preventExtensions and defineProperty calls in the compiler, and check the pending branch step1r-land before changing anything. The witness is a shapes-options test program that also freezes an unrelated object; done means the Object.create family births stay enabled in that program. This is cross-cutting compiler analysis that the coordinator has already decided, so it is not a newcomer task.
Written by the indexing model from the issue text.
Description
Object-model step 1 (the Object.create(literal) families, PR pending from branch step1r-land) decides from three program-wide census facts whether a key add on an Object.create(P) family can be intercepted:
- names given by
defineProperty-style calls; - property definitions the scan can't name;
- any freeze, seal or preventExtensions.
The rule is coarse. One freeze, relink or unnamed define anywhere in the program turns off every such family, even when the target can't be any family's prototype.
Fix forward: narrow each fact to the targets it can reach (P's family, or the families whose prototype set includes the written object), so that unrelated freezes and defines keep the families on. The witness is shapes-options plus a program that also freezes an unrelated object: the family births must stay on.
Coordinator decision: fix forward, not blocking.
- Dominant language
- Rust
- Stars
- 4.9k
- Forks
- 166
- Avg merge
- 2h 54m
- Merged PRs (30d)
- 922
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PerryTS/perry
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 3 days
-
[BUG] Filename sequence expansion (`+`) panics on numeric values exceeding `i32::MAX`Possibly taken @muntasir-396 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CCExtractor/ccextractor#2402 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100