-
Notifications
You must be signed in to change notification settings - Fork 224
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
Mark SPI slave as unstable #2853
Conversation
@@ -216,7 +216,9 @@ macro_rules! unstable { | |||
}; | |||
} | |||
|
|||
unstable! { | |||
pub(crate) use unstable_module; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to rename the macro, otherwise I couldn't re-export it.
@@ -91,16 +93,17 @@ const MAX_DMA_SIZE: usize = 32768 - 32; | |||
/// SPI peripheral driver. | |||
/// | |||
/// See the [module-level documentation][self] for more details. | |||
#[instability::unstable] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
given the whole module is unstable this is just to make the docs look nicer, right? (just in case I am missing something important here)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That, and we'll have to explicitly go through these once we commit to stabilizing SPI slave. FWIW rustdoc tends to ignore these, too, in places.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.