diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2021-01-03 17:09:08 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-01-03 17:09:08 +0100 |
| commit | 2072e117304da97ea1c7df052519f6dc3777b7ff (patch) | |
| tree | e6a934b47776bae0292922262c8124edfc40e781 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | 2686daa7791865d7970fba2b9d6e6db279666a41 (diff) | |
| parent | 6cf47ff4f0ed0395343c97dddbd278281189f446 (diff) | |
| download | rust-2072e117304da97ea1c7df052519f6dc3777b7ff.tar.gz rust-2072e117304da97ea1c7df052519f6dc3777b7ff.zip | |
Rollup merge of #80591 - lcnr:incomplete-features, r=RalfJung
remove allow(incomplete_features) from std cc https://github.com/rust-lang/rust/pull/80349#issuecomment-753357123 > Now I am somewhat concerned that the standard library uses some of these features... I think it is theoretically ok to use incomplete features in the standard library or the compiler if we know that there is an already working subset and we explicitly document what we have to be careful about. Though at that point it is probably better to try and split the incomplete feature into two separate ones, similar to `min_specialization`. Will be interesting once `feature(const_evaluatable_checked)` works well enough to imo be used in the compiler but not yet well enough to be removed from `INCOMPLETE_FEATURES`. r? `@RalfJung`
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions