antoinevg

I currently have an `AsyncClone` trait in the [antoinevg/nonblocking](1832) branch: https://github.com/ockam-network/ockam/blob/cdf5b781edaa3f8f2533219227d5ebac3eb60036/implementations/rust/ockam/ockam_core/src/lib.rs#L49-L59 Example: https://github.com/ockam-network/ockam/blob/cdf5b781edaa3f8f2533219227d5ebac3eb60036/implementations/rust/ockam/ockam_vault_sync_core/src/vault_sync.rs#L53-L64

`ockam_core::Result` would be great, there are far too many calls to `.unwrap()` in my implementation right now!

I don't think there's been much discussion yet around the implementation of supervision trees in the runtime apart from @spacekookie 's [PR](https://github.com/build-trust/ockam/pull/968/files). I agree with you that using worker channel...

Resources: * https://book.avr-rust.com/ * https://github.com/avr-rust/awesome-avr-rust

> Oh @twittner `Receiver::close` isn't implemented in `no_std`?? @antoinevg > > I can just go back to wrapping it in an Option but this is a bit strange We can...

> We can probably switch to `futures::channel` on `no_std` rather than using our own impl. I'll take a look at this and open a PR if it's do-able. Ah never...

This will also impact the `no_std` rng implementation in `ockam_core::compat` - hopefully we can find a way to get rid of it and just use the vault provided implementation instead.

#1831

Useful overview of how to get started with smoltcp: * https://github.com/antoinevg/nucleo-h7xx/blob/main/src/ethernet.rs * https://github.com/antoinevg/nucleo-h7xx/blob/main/examples/ethernet.rs I've also got a basic UDP implementation in one of my private repo's I can share.

> - `no_std ockam-node impl:` > - guess, we have a barebones impl for this i.e. a global executor to poll and execute futures. > - For the absolute simplest...