[31m[1mERROR[0m[39m: 
  [31m×[0m I can't generate code that will pass the borrow checker *and* match the
  [31m│[0m instructions in your blueprint:
  [31m│[0m - `app::handler` wants to borrow `app::A`
  [31m│[0m - But, earlier on, `app::b` consumed `app::A` by value
  [31m│[0m 
  [31m│[0m Since I'm not allowed to clone `app::A`, I can't resolve this conflict.
  [31m│[0m
  [31m│[0m   [36mhelp:[0m Allow me to clone `app::A` in order to satisfy the borrow checker.
  [31m│[0m         You can do so by invoking `.cloning(CloningStrategy::CloneIfNecessary)`
  [31m│[0m         on the type returned by `.constructor`.
  [31m│[0m        ☞
  [31m│[0m           ╭─[[36;1;4msrc/lib.rs[0m:36:1]
  [31m│[0m        [2m36[0m │     let mut bp = Blueprint::new();
  [31m│[0m        [2m37[0m │     bp.constructor(f!(crate::a), Lifecycle::RequestScoped);
  [31m│[0m           · [35;1m                   ──────┬─────[0m
  [31m│[0m           ·                          [35;1m╰── The constructor was registered here[0m
  [31m│[0m        [2m38[0m │     bp.constructor(f!(crate::b), Lifecycle::RequestScoped);
  [31m│[0m           ╰────
  [31m│[0m   [36mhelp:[0m Consider changing the signature of `app::b`.
  [31m│[0m         It takes `app::A` by value. Would a shared reference, `&app::A`, be
  [31m│[0m         enough?
  [31m│[0m   [36mhelp:[0m If `app::A` itself cannot implement `Clone`, consider wrapping it in
  [31m│[0m         an `std::sync::Rc` or `std::sync::Arc`.