]> git.lizzy.rs Git - rust.git/commit - compiler/rustc_session/src/options.rs
Rollup merge of #107103 - compiler-errors:new-solver-evaluate_obligation, r=lcnr
authorMatthias Krüger <matthias.krueger@famsik.de>
Sat, 28 Jan 2023 04:20:16 +0000 (05:20 +0100)
committerGitHub <noreply@github.com>
Sat, 28 Jan 2023 04:20:16 +0000 (05:20 +0100)
commit3b6593a0b4e41d680ddc196ce47ee649be62a660
treecd004d5a7c96e8da4ffd779424802ac28e161448
parent28188d17ba2eb60fb956a22ef4b0cb017dfe66b4
parent5bfd90efd121cace34bccdf6fe47578b2202bdf9
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.