`rvf-manifest` pulls in `std` transitively via `crc32c`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- embedded-iot
Research direction
Start with crates/rvf/rvf-manifest/src/lib.rs to confirm the conditional no_std setup, then inspect the crc32c dependency in crates/rvf/rvf-manifest/Cargo.toml. Check the dependency's no_std support and verify the result by building rvf-manifest for a no_std or bare-metal target; done means the crate compiles without pulling in std.
Written by the indexing model from the issue text.
Description
This crate supports no_std conditionally:
https://github.com/ruvnet/RuVector/blob/4b59352aabc8cc7c2efb04721e9edd1bd244be31/crates/rvf/rvf-manifest/src/lib.rs#L10
But one of its dependencies (crc32c, version 0.6.8) does not support no_std and pulls in std transitively:
https://github.com/ruvnet/RuVector/blob/4b59352aabc8cc7c2efb04721e9edd1bd244be31/crates/rvf/rvf-manifest/Cargo.toml#L20
As a result, builds targeting bare-metal or other no_std-only targets fail to compile, even though the crate itself contains no direct std usage.
- Dominant language
- Rust
- Stars
- 4.5k
- Forks
- 603
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 56
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 ruvnet/RuVector
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
adr phase-w4-3 pir stretch wave-4
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-challenge/player_rust#22 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
foundry-rs/foundry#17175 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/copilot-sdk#2793 ·
Maintainers usually reply within 1 day