multiformats / multiformats/multicodec
Table: Application specific ranges
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 383
- Forks
- 221
- Avg merge
- 24d 6h
- Merged PRs (30d)
- 1
Description
We were going to keep some application specific ranges. I'm not finding them in the table. We should add them back.
Ideally we should have a function that keeps some numbers within every varint size. Meaning that:
- a 1-byte varint should have a few value reserved for app-specific codes.
- a 2-byte varint should have some too, many more than 1-byte.
- etc.
Effectively: come up with a function appSpecific(code int) bool that:
- assigns some values at every varint range
- is simple to understand
For example, one such function could be:
func appSpecific(code int) bool {
return code % 127 > (127 - 8)
// keeps 8 codes every 128.
}
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
The issue names the multicodec table and an appSpecific(code int) bool function, but no files or tests. Locate the table and varint implementation first, then determine how reserved values should be represented at each varint size. Done means the table includes application-specific ranges and tests cover the chosen allocation across sizes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100