rust/tests/ui/parser/circular_modules_main.stderr

error: circular modules: $DIR/circular_modules_main.rs -> $DIR/circular_modules_hello.rs -> $DIR/circular_modules_main.rs
  --> $DIR/circular_modules_hello.rs:4:1
   |
LL | mod circular_modules_main;
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 1 previous error
expand: Move module file path stack from global session to expansion data Also don't push the paths on the stack directly in `fn parse_external_mod`, return them instead. 2021-02-21 19:15:43 +03:00			`error: circular modules: $DIR/circular_modules_main.rs -> $DIR/circular_modules_hello.rs -> $DIR/circular_modules_main.rs`
			`--> $DIR/circular_modules_hello.rs:4:1`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`\|`
expand: Move module file path stack from global session to expansion data Also don't push the paths on the stack directly in `fn parse_external_mod`, return them instead. 2021-02-21 19:15:43 +03:00			`LL \| mod circular_modules_main;`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00
Keep track of parse errors in `mod`s and don't emit resolve errors for paths involving them When we expand a `mod foo;` and parse `foo.rs`, we now track whether that file had an unrecovered parse error that reached the end of the file. If so, we keep that information around. When resolving a path like `foo::bar`, we do not emit any errors for "`bar` not found in `foo`", as we know that the parse error might have caused `bar` to not be parsed and accounted for. When this happens in an existing project, every path referencing `foo` would be an irrelevant compile error. Instead, we now skip emitting anything until `foo.rs` is fixed. Tellingly enough, we didn't have any test for errors caused by `mod` expansion. Fix #97734. 2024-12-05 21:19:08 +00:00			`error: aborting due to 1 previous error`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00