chore: claim the no-std categories on crates.io - #97
Merged
Conversation
The crate now declares #![cfg_attr(not(test), no_std)] and CI builds it for thumbv7em-none-eabihf, so both claims hold and are enforced. no-std::no-alloc applies as well: runtime code never allocates, and the library exposes no allocating container. The no-std keyword is deliberately not claimed. Keywords are capped at five, that page carries 2400 crates, and buying a slot there would cost subnet, whose page carries nine and where this crate is actually visible.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
categoriesgainsno-stdandno-std::no-alloc.Both claims now hold and are enforced: #95 declared
#![cfg_attr(not(test), no_std)]and added a CI job that builds the library forthumbv7em-none-eabihf, a target with nostdat all.no-allocapplies too -- runtime code never allocates and the library exposes no allocating container.The
no-stdkeyword is deliberately not claimed. Keywords are capped at five; that keyword's page carries 2400 crates, so it is not a discovery surface, and buying a slot there would costsubnet, whose page carries nine and where this crate is actually visible. Categories are browsable and filterable, which is where theno-stdsignal does work.Like any keyword or category change, this only takes effect on the next publish.