rust-embedded / rust-embedded/heapless
Feature gating types
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 253
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
I've used heapless in a number of applications now and I often find I only use a subset of its functionality (e.g. just Vec and String).
It would be nice if we could gate types behind feature flags. For simpler use cases this could eliminate all build and runtime dependencies. This keeps the dependency graph lean which can be an important factor when evaluating crates.
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
No files, tests, or entry points are named in the issue. Start by reviewing heapless's crate structure and current feature configuration, then map the types that would need independent feature gates. Done means selected types can be enabled separately while simpler configurations avoid unnecessary build and runtime dependencies, with coverage for the supported combinations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100