stacks-network / stacks-network/stacks-core
Type Aliases / Custom Types
Open
Nobody has claimed this yet.
clarity-next-candidate
clarity-non-backwards-compatible
clarity-type-checker
- Dominant language
- Rust
- Stars
- 3.1k
- Forks
- 762
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 76
Description
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.
Research direction
Start by reading the two linked context issues, stacks-blockchain#1171 and stacks-blockchain#1638, to determine what type aliases or custom types are required. Then inspect the relevant Rust areas identified there and clarify the intended scope and acceptance criteria before making changes; the issue currently names no files, tests, or definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100