From ef77d8375130d12678d4b2316cc1708c90349dad Mon Sep 17 00:00:00 2001 From: Florian Diebold Date: Wed, 1 May 2019 17:13:33 +0200 Subject: Document the peculiarity of the solver query a bit Also remove the only remaining mention of chalk outside of the ty::traits module. --- crates/ra_hir/src/ty/traits.rs | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'crates/ra_hir/src/ty') diff --git a/crates/ra_hir/src/ty/traits.rs b/crates/ra_hir/src/ty/traits.rs index acb69683c..ac31ca2f6 100644 --- a/crates/ra_hir/src/ty/traits.rs +++ b/crates/ra_hir/src/ty/traits.rs @@ -10,13 +10,15 @@ use self::chalk::{ToChalk, from_chalk}; mod chalk; +pub(crate) type Solver = chalk_solve::Solver; + #[derive(Debug, Copy, Clone)] struct ChalkContext<'a, DB> { db: &'a DB, krate: Crate, } -pub(crate) fn solver(_db: &impl HirDatabase, _krate: Crate) -> Arc> { +pub(crate) fn solver(_db: &impl HirDatabase, _krate: Crate) -> Arc> { // krate parameter is just so we cache a unique solver per crate let solver_choice = chalk_solve::SolverChoice::SLG { max_size: 10 }; Arc::new(Mutex::new(solver_choice.into_solver())) @@ -48,7 +50,7 @@ fn solve( goal: &chalk_ir::UCanonical>, ) -> Option { let context = ChalkContext { db, krate }; - let solver = db.chalk_solver(krate); + let solver = db.solver(krate); let solution = solver.lock().unwrap().solve(&context, goal); eprintln!("solve({:?}) => {:?}", goal, solution); solution -- cgit v1.2.3