Wilco Kusee

Alright, changed it to `Ok(Ambig)`. As for refactoring, would it be useful to add `Solution::QuantumExceeded`, like `AnswerResult::QuantumExceeded` in chalk-engine?

This hangs on a `Implements(Closure: RecurFn

> Yeah, and it's really annoying that we can't easily reproduce these in the Chalk test harness... Might this be [rust-lang/chalk#688](https://github.com/rust-lang/chalk/issues/688) again? I was going to say no, but looking...

> It would be nice to get better debug output about the closure - closure kind, inputs/output getting lowered, upvars. That's in the `RustIrDatabase` callbacks, [`closure_inputs_and_output` and `closure_upvars`](https://github.com/rust-analyzer/rust-analyzer/blob/9719ce9fc731a400c9744ba1a6569e978c1a97e7/crates/hir_ty/src/traits/chalk.rs#L288-L311), right? It...

Looks like a chalk issue, since the solver gets stuck in a loop. Relevant logs with `RA_LOG=hir_ty=trace`: ``` [INFO hir_ty::traits] trait_solve_query(Normalize(| -> ?0.1 as FnOnce,)>>::Output => ?0.2)) [DEBUG hir_ty::traits] solve...

So your use case is that you're interfacing with `gilrs` directly and want to use `gilrs::GamepadId` directly, right? I can see how workarounds like calling a function from both your...