Remove use of const traits (and feature(effects)) from stdlib#126552
Conversation
|
r=me when ci is green Note for anyone whose nightly code has regressed because we removed const traits from libstdPlease pin your nightly version to |
This comment has been minimized.
This comment has been minimized.
|
Could also mark the features as incomplete now as then they won't be usable in libcore accidentally |
|
Yeah, good idea. Will require adding a bunch of |
|
@rustbot author |
|
☔ The latest upstream changes (presumably #116088) made this pull request unmergeable. Please resolve the merge conflicts. |
|
I made @rustbot ready |
This comment has been minimized.
This comment has been minimized.
|
r=me after making tests pass |
|
@rustbot author |
|
@bors r=compiler-errors |
|
Looks like the book uses effects in examples |
|
@bors r=compiler-errors |
…iaskrgr Rollup of 3 pull requests Successful merges: - rust-lang#126140 (Rename `std::fs::try_exists` to `std::fs::exists` and stabilize fs_try_exists) - rust-lang#126318 (Add a `x perf` command for integrating bootstrap with `rustc-perf`) - rust-lang#126552 (Remove use of const traits (and `feature(effects)`) from stdlib) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#126552 - fee1-dead-contrib:rmfx, r=compiler-errors Remove use of const traits (and `feature(effects)`) from stdlib The current uses are already unsound because they are using non-const impls in const contexts. We can reintroduce them by reverting the commit in this PR, after rust-lang#120639 lands. Also, make `effects` an incomplete feature. cc `@rust-lang/project-const-traits` r? `@compiler-errors`
The current uses are already unsound because they are using non-const impls in const contexts. We can reintroduce them by reverting the commit in this PR, after #120639 lands.
Also, make
effectsan incomplete feature.cc @rust-lang/project-const-traits
r? @compiler-errors