-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Dismantle std::unstable #1457
Comments
I have made it so that these mods don't appear in the documentation, so that's a start |
Punting on this for 0.2 |
Is this still something we want? |
@brson, how much of this was done with the move of things into |
Still more to discuss here; tagging as priority so we can have that discussion. |
@alexcrichton some. e.g. a lot of lang items and intrinsics are under unstable. A lot of what is currently in unstable will move out and be tagged |
This is to cleanout the std::unstable module and use the appropriate unstable attribute. This mutex module is **not** supposed to be used outside of the compiler/std. This change is according to rust-lang#1457 and comment rust-lang#1457 (comment) [breaking-change]
This leaves a deprecated reexport in place temporarily. Closes rust-lang#1457.
This leaves a deprecated reexport in place temporarily. Closes rust-lang#1457.
Fix simd_select_bitmask on big-endian systems
…temporary, just directly create the rvalue we need (rust-lang#1457)
Co-authored-by: Yuki Okushi <jtitor@2k36.org>
Co-authored-by: Yuki Okushi <jtitor@2k36.org>
core and std have extfmt and test modules which just provide compiler support and aren't intended to provide a user-facing API. We should have some convention for where they should be hidden away. In particular, "test" is a module where I would like to put useful things for writing tests, not the infrastructure code that's there now.
The text was updated successfully, but these errors were encountered: