version 1.0 tracking issue checklist
Open
Nobody has claimed this yet.
help wanted
question
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 202
- PR merge metrics
- No merged PRs in 30d
Description
We're still seeing minor breakage, which is good, especially the usize stuff.
I'd like to start a checklist of things to do before 1.0.
I'll add them here as we add things.
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 no files, tests, or concrete checklist items. Begin by reviewing the current minor breakage and usize-related work in the Rust crate, then define the 1.0 checklist and clear acceptance criteria in this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100