object model 3a part 2: http/stream instance fields (_header, _events, destroyed) walk the prototype chain (~106k walks per fastify run)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- node.js, rust, typescript
- Domain
- compilers, performance
Research direction
Start with qb6:/root/claude-lanes/p3bii-PROGRESS.md and p3bii/work/keys.tsv, then trace the object model step 6, 3a part 2 instance layout work for the classes named in the issue. Check how constructor-set fields are represented at object creation and use the fastify inject workload to compare prototype walks. Done means _header, _events, and destroyed are available as instance slots at birth and their reads no longer walk the prototype chain.
Written by the indexing model from the issue text.
Description
Measured in object-model step 6 slice 3b-ii phase 1 on main b8026ceb61, fastify inject (light-my-request): about 106k of the 397k resolve_inherited_field_from_prototype walks per run are for _header (31.8k), _events (42.4k) and destroyed (10.6k)…, read on light-my-request Response / ServerResponse instances.
In node these are own fields that the constructors put on the instance (OutgoingMessage, EventEmitter.init, stream state), so node never walks a chain for them. In perry the instance doesn't carry them, so every read misses its own fields and walks Response → ServerResponse → OutgoingMessage → Stream → EventEmitter → Object.prototype; _header misses all six.
Fix: instance layouts for these classes (object-model step 6, 3a part 2, owner ump), with the constructor-set fields as slots at birth. Slice 3b-ii (the prototype layouts) does not touch instances.
Data: qb6:/root/claude-lanes/p3bii-PROGRESS.md and p3bii/work/keys.tsv.
- 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