What is the motivation for the index-based format?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- api
Research direction
Start by reading the linked ProfilerTrace dictionary and its nested structures in the js-self-profiling proposal. Review the existing discussion and determine whether the proposal explains the motivation for index-based strings in the JavaScript API. Done means the rationale is decided and documented, or the proposal is updated to reflect the decision.
Written by the indexing model from the issue text.
Description
I can understand, in a binary format, using certain arrays of strings, separate from indexed references to them. But the current proposal uses this in its JavaScript API as well, in the ProfilerTrace dictionary and nested structures. I would have expected to see strings directly used in such dictionaries instead. Is this motivated by compression, or ease of certain kinds of processing, or something else?
- Dominant language
- HTML
- Stars
- 207
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Contributor 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 WICG/js-self-profiling
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WICG/js-self-profiling#90 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
WICG/js-self-profiling#86 · 2 comments · 3 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
WICG/js-self-profiling#84 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WICG/js-self-profiling#83 · 1 comment · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WICG/js-self-profiling#81 · 2 comments · 1 reaction ·
All issues in WICG/js-self-profiling
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·