Dario Nieuwenhuis

I'm going to close this because I don't believe it's worth the effort given the reasons above, assuming `panic_immediate_abort` allows the same level of debloat. Thanks anyway for the PR,...

> I think since panic_immediate_abort is not appropriate for my use-case Can you expand on why? Is it because you want to still be able to get the location of...

> However, both embedded_hal::digital::ErrorKind and embedded_hal::pwm::ErrorKind only contain one variant Other, which means it is currently completely useless. So I'd suggest to remove these for now, until the need arises....

i'm going to remove this from the 1.0 milestone, It concerns only `embedded-hal-bus`, we can do it in `0.1.1` in a backwards-compatible way (like adding `.set_blah_delays()` methods), or in `0.2`...

- ErrorType is separate even in modules with only 1 trait (like i2c, pwm) to acommodate for future extensions. For example PWM might get a `SetFrequency` trait in the future....

You can already do it now with `delay_[mu]s` and `select` (there's `select` available in several crates, for example `embassy-futures` or `futures`). I'm not sure if we should add this as...

this is more likely a bug in `embassy-net-wiznet`. Do you have a packet capture from the other host that would show whether the ARP requests are coming through or not?

yeah this seems an embassy-net-wiznet issue. please open an issue there. Be warned these "stops working randomly after many hours" issues are super tricky to debug, if you want other...

Smoltcp is primarily designed for embedded systems, running on microcontrollers with no OS, typically around 256kB of RAM. The typical applications don't create many sockets. For example you might have...

You can use SpiBus instead of SpiDevice, managing CS and DC pins manually. The closure design had some downsides (it's not implementable on Linux and some RTOSs, which require specifying...