Skip to content

Clarify what no_std is good for. #23530

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Clarify what no_std is good for. #23530

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions src/doc/trpl/unsafe.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -426,9 +426,13 @@ Current valid options are:

# Avoiding the standard library

By default, `std` is linked to every Rust crate. In some contexts,
this is undesirable, and can be avoided with the `#![no_std]`
attribute attached to the crate.
By default, `std` is linked to every Rust crate. In some contexts, such as
writing a kernel, this is undesirable. Rust's standard library can still be
used when writing things like shared libraries, even when being called into,
as in C.

If you don't want the standard library linked, it can be avoided with the
`#![no_std]` attribute attached to the crate.

```ignore
// a minimal library
Expand Down