mathieu/os-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Better phrasing for hygiene of include macro

Browse source
This commit is contained in:
Gijs Burghoorn 2023-01-05 17:09:05 +01:00
parent eb2980c7f1
commit c30f7c9980
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
library/core/src/macros/mod.rs
View file

@ -1329,10 +1329,11 @@ pub(crate) mod builtin {
/// </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,