nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-01 23:12:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Appease tidy

Browse Source
This commit is contained in:
James Haywood 2023-10-02 19:22:42 -04:00
parent f96cfb533a
commit 0c6d279728
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
library/core/src/macros/mod.rs
View File

@ -719,7 +719,7 @@ macro_rules! unreachable {
/// The difference between `unimplemented!` and [`todo!`] is that while `todo!`
/// conveys an intent of implementing the functionality later and the message is "not yet
/// implemented", `unimplemented!` makes no such claims. Its message is "not implemented".
///
///
/// Also, some IDEs will mark `todo!`s.
///
/// # Panics
@ -806,7 +806,7 @@ macro_rules! unimplemented {
/// The difference between [`unimplemented!`] and `todo!` is that while `todo!` conveys
/// an intent of implementing the functionality later and the message is "not yet
/// implemented", `unimplemented!` makes no such claims. Its message is "not implemented".
///
///
/// Also, some IDEs will mark `todo!`s.
///
/// # Panics
@ -815,7 +815,7 @@ macro_rules! unimplemented {
/// fixed, specific message.
///
/// Like `panic!`, this macro has a second form for displaying custom values.
///
///
/// # Examples
///
/// Here's an example of some in-progress code. We have a trait `Foo`:
@ -849,7 +849,7 @@ macro_rules! unimplemented {
/// // Let's not worry about implementing baz() for now
/// todo!();
/// }
///
///
/// fn qux(&self) -> Result<u64, ()> {
/// // We can add a message to todo! to display our omission.
/// // This will display: