cortex-m VS reitit

I do not have as strong of feelings as your parent, but:

1. A lot of the APIs make use of the typestate pattern, which is nice, but also very verbose, and might turn many people off.

2. The generated API documentation for the lower level crates relies on you knowing the feel for how it generates the various APIs. It can take some time to get used to, especially if you're used to the better documentation of the broader ecosystem.

3. A bunch of the ecosystem crates assume the "I am running one program in ring0" kind of thing, and not "I have an RTOS" sort of case. See the discussion in https://github.com/rust-embedded/cortex-m/issues/233 for example.

For cortex-m support, check out the cortex-m crate

See https://github.com/rust-embedded/cortex-m/tree/master/panic-semihosting

I don't think so. Once a function is compiled, it basically becomes a black box with a type signature so unless sleeping in a function affects its signature, that information is erased. If you pass in some kind of a sleep token that has to be used to sleep, then yeah I think you could enforce it by only being able to get that token in a non-atomic context and making it leak proof.

The Cortex-M crate does something similar, but for proving that you are in an atomic context. Another function that expects a CriticalSection type is then assured that it's running without interrupts enabled.

https://github.com/rust-embedded/cortex-m/blob/master/src/in...

I would build the CLJS for your game logic. Then I would build the backend server separately with API endpoints your front end to talk to. https://github.com/metosin/reitit is a pretty good option.

A significant feature of reitit is that routes are composed of simple vectors and maps. That means you can pre-process that data structure however you want before building the router.

You might look at the examples on the Reitit page. Reitit seems to be the emerging library for routing, and it does get you most of the way there, no matter which direction you are looking to go..

for runtime validation & coercion, you can use the pedestal-utilities from reitit which support all of spec, schema and malli. For dev-time var instrumentation (static & dynamic), there are several ways to add those to existing or 3rd party codebases.