update use of feature flags
This commit is contained in:
parent
5d97ada1ec
commit
11d16c4082
218 changed files with 227 additions and 228 deletions
|
@ -1,7 +1,6 @@
|
|||
//! The next-generation trait solver, currently still WIP.
|
||||
//!
|
||||
//! As a user of rust, you can use `-Ztrait-solver=next` or `next-coherence`
|
||||
//! to enable the new trait solver always, or just within coherence, respectively.
|
||||
//! As a user of rust, you can use `-Znext-solver` to enable the new trait solver.
|
||||
//!
|
||||
//! As a developer of rustc, you shouldn't be using the new trait
|
||||
//! solver without asking the trait-system-refactor-initiative, but it can
|
||||
|
@ -248,7 +247,7 @@ impl<'tcx> EvalCtxt<'_, 'tcx> {
|
|||
return None;
|
||||
}
|
||||
|
||||
// FIXME(-Ztrait-solver=next): We should instead try to find a `Certainty::Yes` response with
|
||||
// FIXME(-Znext-solver): We should instead try to find a `Certainty::Yes` response with
|
||||
// a subset of the constraints that all the other responses have.
|
||||
let one = responses[0];
|
||||
if responses[1..].iter().all(|&resp| resp == one) {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue