rust/src/test/ui/resolve/visibility-indeterminate.stderr

error[E0578]: cannot determine resolution for the visibility
  --> $DIR/visibility-indeterminate.rs:5:8
   |
LL | pub(in ::bar) struct Baz {}
   |        ^^^^^

error: cannot find macro `foo` in this scope
  --> $DIR/visibility-indeterminate.rs:3:1
   |
LL | foo!();
   | ^^^

error: aborting due to 2 previous errors
resolve: Move late resolution into a separate visitor Move `Resolver` fields specific to late resolution to the new visitor. The `current_module` field from `Resolver` is replaced with two `current_module`s in `LateResolutionVisitor` and `BuildReducedGraphVisitor`. Outside of those visitors `current_module` is replaced by passing `parent_scope` to more functions and using the parent module from it. Visibility resolution no longer have access to later resolution methods and has to use early resolution, so its diagnostics in case of errors regress slightly. 2019-08-05 13:18:50 -05:00			`error[E0578]: cannot determine resolution for the visibility`
			`--> $DIR/visibility-indeterminate.rs:5:8`
			`\|`
			`LL \| pub(in ::bar) struct Baz {}`
			`\| ^^^^^`

resolve: Remove `!` from "cannot find" diagnostics for macros 2019-09-15 05:12:14 -05:00			error: cannot find macro `foo` in this scope
resolve: Move late resolution into a separate visitor Move `Resolver` fields specific to late resolution to the new visitor. The `current_module` field from `Resolver` is replaced with two `current_module`s in `LateResolutionVisitor` and `BuildReducedGraphVisitor`. Outside of those visitors `current_module` is replaced by passing `parent_scope` to more functions and using the parent module from it. Visibility resolution no longer have access to later resolution methods and has to use early resolution, so its diagnostics in case of errors regress slightly. 2019-08-05 13:18:50 -05:00			`--> $DIR/visibility-indeterminate.rs:3:1`
			`\|`
			`LL \| foo!();`
			`\| ^^^`

Provide a span if main function is not present in crate Unfortunately, the diagnotic machinery does not cope well with an empty span which can happen if the crate is empty, in which case we merely set a spanless note. 2019-09-08 12:06:49 -05:00			`error: aborting due to 2 previous errors`
resolve: Move late resolution into a separate visitor Move `Resolver` fields specific to late resolution to the new visitor. The `current_module` field from `Resolver` is replaced with two `current_module`s in `LateResolutionVisitor` and `BuildReducedGraphVisitor`. Outside of those visitors `current_module` is replaced by passing `parent_scope` to more functions and using the parent module from it. Visibility resolution no longer have access to later resolution methods and has to use early resolution, so its diagnostics in case of errors regress slightly. 2019-08-05 13:18:50 -05:00