microsoft / microsoft/rust-guidelines
M-TARGET-FEATURES ... must not prevent a crate from compiling
Open
Nobody has claimed this yet.
easy-pr
request
- Dominant language
- Rust
- Stars
- 200
- Forks
- 25
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
In other words, in 'normal' library crates there must always be a "pure rust" fallback available that's chosen.
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 repository context for M-TARGET-FEATURES and locating any related guidance or examples for target-specific features. The issue does not name a file or test; done means the guidance clearly requires a pure-Rust fallback so a normal library crate can still compile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100