Danilo Bargen

This can probably be closed, right?

> Currently, in no_std projects it is required to include the std library to test with mocks that return errors Is that a problem? Currently embedded-hal-mock does require std, but...

Well, it's not just the `io` errors. For example, we use `Vec` in a few places in the source (see https://github.com/search?q=repo%3Adbrgn%2Fembedded-hal-mock%20vec&type=code), and probably some other `std`-only data structures as well....

I think the `MockError::Io` should be easy to replace with a custom error variant. Right now I don't know what the implications of making this library `no_std` are. If you...

I think everything should work fine now, but the PR is currently blocked on #352.

Hm, so you're triggering some of the panics from C code in your test suite? Can you elaborate what that use case looks like?

Yeah, panics across FFI boundaries are not supported. I guess we could wrap the assertion macros with our own macros, and swap them out in case in case you do...

> I've tested Tutanota and Element flatpak which both have updated to Electron 26 and the crashes are gone entirely. :) Are sure they haven't simply disabled Wayland? If I...

A bit offtopic, but: A simple way to test, if a window uses Xorg or Wayland, is to launch `xeyes` and move the cursor over the window. If the eyes...

Or alternatively an [AppImage](https://appimage.org/).