Don't follow include! expansion to origin

[RReverser]

include! errors are special in the sense that caller side is not useful for reporting all the syntax / type errors originating in included file (as you're getting tons of messages pointing to the same line where include!(...) occurs).

This change adds special case that keeps errors bound to their original location if it was include!d.

Before:

After:

[KalitaAlexey]

Hello @RReverser,
I need to check it before I can merge it.
Thank you for this.

[RReverser]

@KalitaAlexey Sure, let me know if you find anything.

[KalitaAlexey]

Could you provide an example?
I have no time now for imaging it itself.

[RReverser]

Well just any include!("somefile.rs") where somefile.rs is garbage (has syntax or type errors on various lines).

[KalitaAlexey]

@RReverser,
I checked it twice.

First time

build.rs:

use std::env;
use std::fs::File;
use std::io::Write;
use std::path::Path;

fn main() {
    let out_dir = env::var("OUT_DIR").unwrap();
    let dest_path = Path::new(&out_dir).join("hello.rs");
    let mut f = File::create(&dest_path).unwrap();

    f.write_all(b"
        pub dfn message() -> &'static str {
            \"Hello, World!\"
        }
    ").unwrap();
}

main.rs:

include!(concat!(env!("OUT_DIR"), "/hello.rs"));

fn main() {
    let x = 5;
    let y = 6;
    let u = 7;
}

It showed errors in hello.rs.

Second time

main.rs:

include!("f.rs");

fn main() {
    let x = 5;
    let y = 6;
    let u = 7;
}

f.rs:

s

It showed errors in f.rs.

---

So I don't know what problem you have.

[RReverser]

Oh right, syntax errors originate in correct place because otherwise include! can't even parse that file, it's type checker and other errors that don't.

[RReverser]

Example with multiple errors

[KalitaAlexey]

@RReverser,
I will check it.
Thanks.