-
Notifications
You must be signed in to change notification settings - Fork 13k
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.
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
Clarify what #![no_std] is useful for #20537
Comments
servo/html5ever#63 proposes to drop |
I think it's still useful for libraries that want to work in environments where |
What makes std not work in a kernel? |
|
You'd probably want to avoid |
Is merely linking against libstd problematic, if these modules are not used? |
I think so, since you'd probably end up pulling in a dynamic dependency on glibc. |
This is basically a doc bug. cc @steveklabnik |
I'm moving this thread to rust-lang/rfcs#1005, given that it's an unstable feature. |
I’ve initially made rust-wtf8 use
#![no_std]
out of the theoretical concern that potential users (maybe html5ever) would want#![no_std]
as well. (And because it wasn’t hard.)But now that the runtime was removed, what are the real benefits of using
#![no_std]
? The html5ever source has a "This helps us make a C-friendly library." comment. @kmc, how does it help?The text was updated successfully, but these errors were encountered: