Wilfried Chauveau

This is a good question, I'm trying to understand that. (thank you for leaving this message as it helps track when it started to fail).

~~Ok, CI did not because it ignores changes in docs.~~ Actually it should have at least ran the "skipped" pipeline instead. I don't know why it's not running yet.

Thank you for your patience.

This has been investigated and it revealed that the fault was due to a use of `malloc` before `malloc_prepare`. Related to https://github.com/zephyrproject-rtos/zephyr/pull/74579 Malloc has been removed from the upstream driver:...

We could keep the branch with the generated sources as the visible branch but ask for contributions to be made on a dev branch. This'd keep the best of both...

I need to try a few thing, to make sure I'm not missing some inference subtleties. EDIT: I made this: https://github.com/ithinuel/rp-hal/commit/90c6c820090c796a3e6551c03acfcc5f10f9ad34 I only managed to get rid of the turbofish...

I'm not too attached to that parameter TBH. On a setup with multiple spi peripheral with the rp2040 as one controller on the bus, you may need to change the...

True, I’m mostly done with the tests of the blocking APIs. I’m currently testing & fixing the async implementation. I’d like to reduce the "colored" part of the implementation before...

Always using the trait doesn't really solve the problem either if you have both sync and async traits in scope. You still need to disambiguate. For inherent methods, I'd probably...

> Is this really an issue? Why would you import both the sync and the async traits? > > If it's a rare situation, then manual disambiguation is fine IMHO....