Wilfried Chauveau

Slack does that too, this comes extremely handy especially for ADHD brains!

@jamesmunns is this crate still maintained?

I'm happy to help keep the light on, but I cannot commit for maintaintership as my availability is pretty volatile these days. Also, I'm closing this PR in favour of...

It does not work with `impl Trait` as return time either. From what I understand it is because the return type of the generator is used to define a field...

The first error is an issue with proc macros & `rust-analyzer`'s macro expansion's feature. You can disable that error by setting `"rust-analyzer.procMacro.enable": false` in your config. The second error is...

Wouldn't an `fn is_writable(&self) -> bool` method be simpler?

Is there anything else to do on this PR? (rebase/reach compromise/clone?)

For what it's worth, I am running a nostd_async executor on each core on wilskeeb. https://github.com/ithinuel/wilskeeb/blob/develop/firmware/src/main.rs#L544-L562 Tasks don't get passed from one core to the other because that'd involve some...

I think the point of the peripheral taking ownership of the pins is to be able to guaranty that the pins will remain in a valid state for the peripheral...

IMHO, rp-hal-boards is good enough.