Ryan Summers

The more I think about it, the more @jordens is convincing me that we should revert to 7ba884993fea57c3661d0f9d7c3cdca639a48701, specifically because that the `Interface` can be owned by the runner without...

> Should the runner own the interface or should it have a `poll(&mut intf, &mut ctx)` method? My opinion here is that the interface is much more closely tied to...

While I understand the desire to have `portable-atomics` out of your individual dependency graph, I'm not sure this is the best approach for the broader audience. The whole point of...

Yeah I'm also not sure this makes sense to allow. Can you elaborate on what the necessary use case is here?

Both myself and another Matrix user noted that our projects seemed to freeze up when calling `UsbDevice.freeze()`. We both were able to resolve it by updating the HAL that we...

I am very okay with a generic socketaddr type myself, as I've had these exact same issues during implementation. I don't see any specific benefit to using `no-std-net`, since we...

However, how would a library that is agnostic to the underlying stack know how to construct and use these addresses? I.e. https://github.com/quartiq/minimq/blob/master/src/network_manager.rs, where we don't know what stack we're running...

I would love to use `core::net`, but it's still nightly-only behind `feature(ip_in_core)`

Closing this as resolved by https://github.com/rust-embedded-community/embedded-nal/pull/102, as we now use the freshly-stabilized `core::net` :) If my assessment is wrong here, feel free to reopen!

Check out https://github.com/quartiq/smoltcp-nal/pull/46 for an example implementation using smoltcp