Sorry if this is the wrong place:
The Cortex-M Quickstart guide Docs.rs build 0.3.4 is failing with the following:
`
error[E0658]: The attribute 'panic_implementation' is currently unknown to the compiler and may have meaning added to it in the future (see issue #29642)
--> .cargo/registry/src/github.com-1ecc6299db9ec823/panic-semihosting-0.3.0/src/lib.rs:71:1
|
71 | #[panic_implementat

Right now, [README.md][readme] includes copy-pasted code from sample code in [src/example/][src/example] tree, but they're not kept in-sync automatically.

Ideally, we would have a process for automatically including code samples, e.g., via some preprocessing since it's probably not possible to do it dynamically, so that we can avoid having to see them diverge, e.g., as can be seen in issue

We utilize a priority queue to handle our interrupts by priority - we take the next highest priority off the stack first.

I was trying to build the Renode from scratch on empty machines just to see what exact steps are needed.

I used this document:
https://renode.readthedocs.io/en/latest/advanced/building_from_sources.html

And followed the command line approach to build whole renode packages and including the Robot framework (it was the build.sh -p and not the MonoDevelop/VisualStudio aproach).

Fo

We should follow the terminology used in the CAN FD specification, where the old CAN standard is termed "Classic CAN". So the following should be renamed into TypeClassic:

https://github.com/UAVCAN/libuavcan/blob/1e0d947132b565601612f7cae528ce31f492f9f9/libuavcan/include/libuavcan/media/can.hpp#L58

The README should be updated to reflect the current state of the examples. It should explain how to build / run them and show differences between interpreted examples and compiled examples.