Rollup merge of #105784 - yanns:update_stdarch, r=Amanieu

[rust.git] / library / core / src / macros / mod.rs

diff --git a/library/core/src/macros/mod.rs b/library/core/src/macros/mod.rs
index ff80d1160f65e6d2413cb0a94f78af99c4c7b775..3b026bc0e0f381bd23b847f3c9ecd0fcf0ca315b 100644 (file)
--- a/library/core/src/macros/mod.rs
+++ b/library/core/src/macros/mod.rs
@@ -1315,9 +1315,6 @@ macro_rules! cfg {
 
     /// Parses a file as an expression or an item according to the context.
     ///
-    /// <div class="example-wrap" style="display:inline-block">
-    /// <pre class="compile_fail" style="white-space:normal;font:inherit;">
-    ///
     /// **Warning**: For multi-file Rust projects, the `include!` macro is probably not what you
     /// are looking for. Usually, multi-file Rust projects use
     /// [modules](https://doc.rust-lang.org/reference/items/modules.html). Multi-file projects and
@@ -1326,13 +1323,11 @@ macro_rules! cfg {
     /// explained in the Rust Book
     /// [here](https://doc.rust-lang.org/book/ch07-02-defining-modules-to-control-scope-and-privacy.html).
     ///
-    /// </pre>
-    /// </div>
-    ///
-    /// If the included file is parsed as an expression, it is placed in the surrounding code
-    /// [unhygienically](https://doc.rust-lang.org/reference/macros-by-example.html#hygiene). This
-    /// could result in variables or functions being different from what the file expected if there
-    /// are variables or functions that have the same name in the current file.
+    /// The included file is placed in the surrounding code
+    /// [unhygienically](https://doc.rust-lang.org/reference/macros-by-example.html#hygiene). If
+    /// the included file is parsed as an expression and variables or functions share names across
+    /// both files, it could result in variables or functions being different from what the
+    /// included file expected.
     ///
     /// The included file is located relative to the current file (similarly to how modules are
     /// found). The provided path is interpreted in a platform-specific way at compile time. So,