As reported in #57, generated mock implementations will not compile with strict concurrency checking in case of Sendable protocols.
Changing the mocker variable to a let constant and adding @unchecked Sendable to the Mocker class will resolve the issue. @unchecked Sendable is safe to use as Mocker has its own synchronisation implemented for all mutations inside.
As reported in #57, generated mock implementations will not compile with strict concurrency checking in case of
Sendableprotocols.Changing the mocker variable to a
letconstant and adding@unchecked Sendableto theMockerclass will resolve the issue.@unchecked Sendableis safe to use as Mocker has its own synchronisation implemented for all mutations inside.