Guillaume E

Thanks for setting up the list and starting cleaning up the low-hanging fruits! My comment would go in the opposite direction, but is also quite hypothetical at this stage. Anyway,...

> I think historically the answer has been "no bar". If it's in the officially released nightly compiler, it's fair game. We've viewed Tock as a project written in the...

> * `core::intrinsics::sqrtf32`, a square root intrinsic. `f32::sqrt` is not present in `core` even though it just calls the intrinsic. This is because on many platforms, the intrinsic expands into...

A relevant part from rust-lang/rfcs#2505 may be the following: > Also, as it's not possible to use inline assembly (`asm!`) on stable the `vsqrt.f32` instruction would have to be invoked...

> Re the first checkbox, there is still some work to do: #625 Thanks for the pointer! I added it to the list.

> RE: debug statements, one "trivial" way to strip code down by a lot is to remove modify the `panic` handler for a board with one that doesn't output any...

To take back your example: > ```rust > pub struct Kernel //... > } > ``` I'm wondering to which extent we could leverage associated types to make things more...

Another example that I just remembered with dynamic dispatch is the `ProcessRestartPolicy`. Again, even though each board is instantiated with (at most) only one restart policy, this policy is stored...

> Would a change like this propagate outside of the kernel crate? When I added `ProcessType`, my initial attempts required changing something, which lead to changing Grant, which lead to...

This may start to side-track a bit from the original issue. But regarding the references to the kernel, a typical capsule look like the following. ```rust struct FooDriver { apps:...