-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for no_std targets #2
Comments
Interesting. I took a quick look around the code base for things that would not work with
|
About |
I'm not sure it'll work like that; the Of course, you could ignore the execution threads altogether and just use a single global list of currently held mutexes, but that doesn't really make sense unless you have no concurrency. In that case deadlocks aren't really a thing anyway. Fundamentally I think the kind of concurrency you have in your |
Support for
#[no_std]
targets will be pretty convenient in kernel development.For
#[no_std]
syncronization primivitves spin crate can be used respectively.The text was updated successfully, but these errors were encountered: