diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-01-28 05:20:16 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-28 05:20:16 +0100 |
| commit | 3b6593a0b4e41d680ddc196ce47ee649be62a660 (patch) | |
| tree | cd004d5a7c96e8da4ffd779424802ac28e161448 /compiler/rustc_codegen_gcc/example/std_example.rs | |
| parent | 28188d17ba2eb60fb956a22ef4b0cb017dfe66b4 (diff) | |
| parent | 5bfd90efd121cace34bccdf6fe47578b2202bdf9 (diff) | |
| download | rust-3b6593a0b4e41d680ddc196ce47ee649be62a660.tar.gz rust-3b6593a0b4e41d680ddc196ce47ee649be62a660.zip | |
Rollup merge of #107103 - compiler-errors:new-solver-evaluate_obligation, r=lcnr
Use new solver in `evaluate_obligation` query (when new solver is enabled) (only when `-Ztrait-solver=next`, of course) ... Does this make sense? It seems to me like it should be reasonable, but maybe there's some reason why this is a bad idea. r? ``@lcnr`` Needs a perf run because I guess this `solver == TraitSolver::Next` check is on a hot path.
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/std_example.rs')
0 files changed, 0 insertions, 0 deletions