A recent change to rustc (https://github.com/rust-lang/rust/issues/74990) changed the behavior of unwinding from a Rust function across an extern C ABI change. Now, that will cause an abort. This is causing Mockall's CI tests to fail. The possible solutions are either:
Require users to specify extern C-unwind instead. This is annoying for users, and it might not be correct for all non-mock functions.
Automatically define the mock functions as C-unwind. This is much better. However, it causes two new problems:
A function pointer to the original C function will now have a different type from a function pointer to the mock function, because the ABI is part of the function pointer's type.
C-unwind does not yet work for variadic functions.
Somehow figure out how to make Mockall work with panic=abort. It's not a problem, as long as no tests are should_panic and no tests ever fail :wink: .
A recent change to rustc (https://github.com/rust-lang/rust/issues/74990) changed the behavior of unwinding from a Rust function across an
extern CABI change. Now, that will cause an abort. This is causing Mockall's CI tests to fail. The possible solutions are either:extern C-unwindinstead. This is annoying for users, and it might not be correct for all non-mock functions.C-unwind. This is much better. However, it causes two new problems:C-unwinddoes not yet work for variadic functions.panic=abort. It's not a problem, as long as no tests areshould_panicand no tests ever fail :wink: .