keyword nostd vs no_std vs category no-std

[gnzlbg]

There are currently 7 crates using the keyword nostd and 104 crates using the keyword no_std in their manifest files:

• https://crates.io/keywords/nostd
• https://crates.io/keywords/no_std

Then there is the category no-std with 223 crates:

• https://crates.io/categories/no-std

Many of the crates using those keywords are not using the no-std category.

With the current state of affairs I need to do 3 independent queries to find crates that work in no_std environments that are relevant to each of my use cases. I'd rather just do 1 query in the no-std category.

Potential actions:

• cargo publish could forbid using nostd and no_std as a keyword from now on and recommend the user to choose the no-std category instead.

• crates.io could map the existing crates that have the nostd or no_std keywords into the no-std category.

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using rust-lang/cargo#6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[gnzlbg]

Is this still relevant?

Yes.

If so, what is blocking it?

Nothing.

[epage]

crates.io manages the relevant validation for this (though we do have rust-lang/cargo#4377). Going to transfer this over to them.