M-TARGET-FEATURES ... must not prevent a crate from compiling

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
build-system

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.

Description

easy-pr request

In other words, in 'normal' library crates there must always be a "pure rust" fallback available that's chosen.

Dominant language
Rust
Stars
200
Forks
25
Avg merge
3m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/rust-guidelines

All issues in microsoft/rust-guidelines

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.