-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Add compilation profiles to std #7282
Labels
A-runtime
Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Comments
Nominating for Well-Covered. |
This was referenced Aug 8, 2013
Closed
Just a bug |
cc @cmr |
Closing, I believe that the libstd facade overrules this direction of making std more portable. Instead of having compilation profiles, we have chosen to have a "pick and choose" situation to select which crates work the best for your particular application. |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Jun 3, 2021
Fix allow on some statement lints changelog: Fix `#[allow(..)]` over statements for [`needless_collect`], [`short_circuit_statement`] and [`unnecessary_operation`] Fixes rust-lang#7171 Fixes rust-lang#7202
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-runtime
Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
We would like the standard library to be compilable for multiple types of environments. Some environments (JS) don't like green threads, some (JS, microcontrollers) don't like threads at all, some (kernels) just need their own implementations of practically everything. Due to some complex interrelationships I don't think it's generally possible to factor all these capabilities out into their own crates, so we'll have to live with compiling std into different 'profiles'.
The text was updated successfully, but these errors were encountered: