-
Notifications
You must be signed in to change notification settings - Fork 158
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
Fixed VectActive::from() returning incorrect value #500
Fixed VectActive::from() returning incorrect value #500
Conversation
Can you rebase this? The CI failure is from an old MSRV |
@newAM, Could you please explain a little more? I forked the repo and made this commit from the v0.7.x branch. |
Oh, sorry, I didn't see that this was targeting |
Oh, Assuming correct implementation for |
Adding these ugly lines in Cargo.toml to fix deps versions did help compiling on 1.38 Or should we better just bump MSRV to 1.60? |
cortex-m-rt says:
|
But this is cortex-m, not cortex-m-rt From v0.7.x branch Readme: Line 14 in bb4a782
|
But how many people use cortex-m without using cortex-m-rt? |
cortex-m has twice as many downloads compared to cortex-m-rt Should I bump the MSRV to 1.60 and remove fixed dependency versions? |
1.59 makes sense, so they are the same. unwrap_unchecked first appeared in 1.58 so that's fine. |
Fixes #499
Fixed
VectActive::from(u8)
now returns correct value for Interrupt variantRefactored
SCB::vect_active()
to useVectActive::from(u8)
and get rid of code duplication