Why do static functions share expectations?

[128f]

Over here I did a test and saw that the tests fail because of the shared expectations.

Is this a design choice, or a technical limitation? If it's the latter, can we find a way to solve it?

[asomers]

static functions' expectations are global, because there's no mock object to own them. With non-static functions, the expectation state is owned by the mock object. But static functions don't have any associated mock object. So you need to synchronize your tests with some kind of Mutex. Here's an example of how to do that: https://github.com/asomers/mockall/blob/master/mockall/examples/synchronization.rs .

[128f]

Thanks. Are there plans to create this kind of functionality inside the generated code?

[asomers]

It's been discussed. However, adding that Mutex internally could lead to an even worse problem: deadlocks. Deadlocks would be very surprising to users who didn't even know that the Mutex existed.