Skip to content

Commit eb2980c

Browse files
committed
Tidy up whitespace
1 parent 0c43b42 commit eb2980c

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

library/core/src/macros/mod.rs

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1312,7 +1312,7 @@ pub(crate) mod builtin {
13121312
/* compiler built-in */
13131313
};
13141314
}
1315-
1315+
13161316
/// Parses a file as an expression or an item according to the context.
13171317
///
13181318
/// <div class="example-wrap" style="display:inline-block">
@@ -1328,19 +1328,19 @@ pub(crate) mod builtin {
13281328
///
13291329
/// </pre>
13301330
/// </div>
1331-
///
1331+
///
13321332
/// If the included file is parsed as an expression, it is placed in the surrounding code
13331333
/// [unhygienically](https://doc.rust-lang.org/reference/macros-by-example.html#hygiene). This
13341334
/// could result in variables or functions being different from what the file expected if there
13351335
/// are variables or functions that have the same name in the current file.
1336-
///
1336+
///
13371337
/// The included file is located relative to the current file (similarly to how modules are
13381338
/// found). The provided path is interpreted in a platform-specific way at compile time. So,
13391339
/// for instance, an invocation with a Windows path containing backslashes `\` would not
13401340
/// compile correctly on Unix.
13411341
///
13421342
/// # Uses
1343-
///
1343+
///
13441344
/// The `include!` macro is primarily used for two purposes. It is used to include
13451345
/// documentation that is written in a separate file and it is used to include [build artifacts
13461346
/// usually as a result from the `build.rs`
@@ -1351,31 +1351,31 @@ pub(crate) mod builtin {
13511351
/// use the [`include_str`] macro as `#![doc = include_str!("...")]` (at the module level) or
13521352
/// `#[doc = include_str!("...")]` (at the item level) to include documentation from a plain
13531353
/// text or markdown file.
1354-
///
1354+
///
13551355
/// # Examples
1356-
///
1356+
///
13571357
/// Assume there are two files in the same directory with the following contents:
1358-
///
1358+
///
13591359
/// File 'monkeys.in':
1360-
///
1360+
///
13611361
/// ```ignore (only-for-syntax-highlight)
13621362
/// ['🙈', '🙊', '🙉']
13631363
/// .iter()
13641364
/// .cycle()
13651365
/// .take(6)
13661366
/// .collect::<String>()
13671367
/// ```
1368-
///
1368+
///
13691369
/// File 'main.rs':
1370-
///
1370+
///
13711371
/// ```ignore (cannot-doctest-external-file-dependency)
13721372
/// fn main() {
13731373
/// let my_string = include!("monkeys.in");
13741374
/// assert_eq!("🙈🙊🙉🙈🙊🙉", my_string);
13751375
/// println!("{my_string}");
13761376
/// }
13771377
/// ```
1378-
///
1378+
///
13791379
/// Compiling 'main.rs' and running the resulting binary will print
13801380
/// "🙈🙊🙉🙈🙊🙉".
13811381
#[stable(feature = "rust1", since = "1.0.0")]

0 commit comments

Comments
 (0)