Index for implementation defined entities
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
The index of implementation defined behavior is crowded with things that do not elicit behavior, such as the values or types associated with specific names. Suggest pulling out all the implementation defined entities into their own index, or perhaps two indices, one for types and another for values, to save prefixing each entry as "type of" or "value of".
Note that this is a more pronounced issue for types than values, so a single index of implementation defined entities may seem the neatest use of space.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the index of implementation-defined behavior in the draft and reviewing how its type and value entries are currently labeled. Compare the proposed single-index and two-index structures, then confirm that implementation-defined entities are separated without losing existing entries or cross-references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100