News for hackers. Stuff that matters.
Re:Rust from a Gopher – Lessons 7, 8 and 9 by pizza234 on Wednesday November 18, 2020 @08:25AM (#25136455)
The `include!` is not intended to be used as a _generic_ inclusion mechanism¹:

> Using this macro is often a bad idea, because if the file is parsed as an expression, it is going to be placed in the surrounding code unhygienically. 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.

¹=https://doc.rust-lang.org/std/macro.include.html

Re:Rust from a Gopher – Lessons 7, 8 and 9 by kd5bjo on Wednesday November 18, 2020 @08:42AM (#25136586)
I fail to see how you draw your conclusion from that statement. It warns about the macro’s potentially surprising behavior, but doesn’t speak to the designers’ intent at all.

`include!` is analogous to C’s `#include`: it textually pastes the file’s contentents in place of the macro, but I can’t think of another way that a textual (vs. semantic) include mechanism would work.