Consider supporting the Stable channel too
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
No files or tests are named. Start by inspecting the crate configuration and current use of const generics, then check whether the project builds on Rust stable; done means stable is the default and const generics are available only through an explicit opt-in.
Written by the indexing model from the issue text.
Description
If possible, you should support the Stable channel by default and then have an opt-in for const generics.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 0
- Avg merge
- 7h 4m
- Merged PRs (30d)
- 1
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.
More from x52dev/tinymap
-
Roadmap to 1.0.0 Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
todo:perf
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
ACP agents get no MCP servers when the thread is created before the project's first worktree loads Openstate:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zed-industries/zed#64611 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
objectionary/phie#154 ·