Update Rust crate mockall to 0.11.3

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
mockall	dev-dependencies	minor	0.9.1 -> 0.11.3

---

Release Notes

asomers/mockall

v0.11.3

Compare Source

v0.11.2

Compare Source

Fixed

• Suppress "dead code" warnings when automocking a struct's private method. It might be used only by other public methods in the same struct. (#​397)

• Fixed using Mockall when a function named Ok is in scope. The anyhow crate, for example, creates a function by this name. (#​389)

v0.11.1

Compare Source

Fixed

• Fixed mocking methods that use Self in their arguments, but not as the receiver. For example, PartialEq::eq has a signature like fn eq(&self, other: &Self) -> bool (#​373)
• Fixed mocking methods that return a reference to a dyn T trait object, when that trait is not already implemented for Box<dyn T>. (#​380)

v0.11.0

Compare Source

Added

• mock! and #[automock] now support unsafe traits. (#​313)

Changed

• Bump predicates to v2.0.1, see all v2 changes in predicates' changelog. (#​325)

Fixed

• Fixed nondeterministic code generation in methods with multiple lifetime parameters. (#​333)

v0.10.2

Compare Source

Fixed

• Fix mocking specializing methods of non-generic structs, a regression in v0.10.0. (#​309)

• Fix mocking generic methods of generic structs returning nonstatic, a regression in v0.10.0. (#​312)

v0.10.1

Compare Source

Fixed

• Fix mocking trait methods whose return values have lifetime parameters, a regression in v0.10.0. (#​304)

v0.10.0

Compare Source

Added

• mock! will now allow both methods and trait impls to be gated with #[cfg()]] attributes. The attributes will be forwarded to all generated code. This allows for example only mocking certain traits on certain OSes. (#​297)

• automock will now automatically generate Debug implementations for traits and structs. mock! will to, if you put #[derive(Debug)] above the struct's name. (#​289)

• Added support for specific impls. A specific impl is an implementation of a trait on a generic struct with specified generic parameters. For example, impl Foo for Bar<i32> as opposed to impl<T> Foo for Bar<T>. Mockall does not yet support generic methods in such traits. (#​274)

Changed

• Mockall is pickier now about how you mock a trait on a generic struct. Previously you could usually omit the generics. Now, they're required. i.e.,

  mock!{
      MyStruct<T: Bounds> {...}
      impl Foo for MyStruct {...}
  }
  

  should now be written as

  mock!{
      MyStruct<T: Bounds> {...}
      impl<T: Bounds> Foo for MyStruct<T> {...}
  }
  

  (#​274)

Fixed

• Fixed setting simultaneous expectations with different generic types on generic methods whose generic parameters appear in neither the arguments nor the return type. (#​272)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.