Basic question — when you're writing a kernel in Rust with its own threading implementation, how does the rust compiler even know what threads are? It has to identify thread boundaries for send/sync, right?
pub fn spawn<F, T>(f: F) -> JoinHandle<T>
where F: Send + 'static + FnOnce() -> T, T: Send + 'static
The same approach can be used in a kernel context, e.g. place bounds on the functions that create (or, at least, initialise interaction between) concurrently executing pieces of code.