pest-parser / pest-parser/pest
Make sure all dependencies have std features disabled
Open
Nobody has claimed this yet.
maintenance
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 307
- Avg merge
- 8h 23m
- Merged PRs (30d)
- 5
Description
Due to https://github.com/rust-lang/cargo/issues/5730, pest cannot be used in any context (build or proc macro) of a no_std crate if any of its dependencies have an std feature enabled.
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 auditing the dependency feature configuration for pest, including dependencies used in build and procedural-macro contexts. Reproduce the no_std failure described in the issue and trace which dependency enables std; done means pest can be used by a no_std crate without any dependency requiring std.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100