Catherine

I'll see if I can take a look later if I can find the time for it, but I have little experience with probe-rs internals and zero experience with nRF5...

> I don't understand why those same tests did not cause the RuntimeError I saw. I'm worried that there is some subtle issue with the order simulator coroutines are being...

> Would you like some help upstreaming the LLVM changes? Sure. The patchset is pretty small now that the saga of enabling `` et al on single-threaded Wasm is complete,...

> Is [YoWASP/llvm-project@c37f6c3](https://github.com/YoWASP/llvm-project/commit/c37f6c36d202f1454181a98a68fda9fb44b45671) effectively the only part that needs to be upstreamed to LLVM? Yes! This isn't a very big or controversial patch. > Also, do you have an already-pending...

I'll try to do a review today; was busy with other things, sorry!

> I actually spent most of the time debugging an `ErrorOutOfMemory` error because my Saleae was plugged into the same USB hub and was hoarding all the bandwidth. Oh yes,...

The end goal of supporting multiple incompatible `smoltcp` versions within one hardware abstraction layer crate is self-evidently desirable and reasonable to pursue. I don't think splitting off the crate `smoltcp-device`...

Or to summarize in a single sentence: it sounds to me like this PR comes with an implied request to support a (partially sparse) N:M mapping of smoltcp-device API variants...

> It's obvious that if a user is stuck with a smoltcp-device 1.0 implementation, they would be locked out of future smoltcp improvements. Just like they are right now, if...

Anyway, let's discuss the possible implementation strategies: 1. smoltcp to smoltcp-device is 1:1, lives in this repo, we get rid of the features in smoltcp-device and bump the minor or...