rust/tests/ui/imports/issue-4366-2.stderr

error[E0412]: cannot find type `Bar` in this scope
  --> $DIR/issue-4366-2.rs:15:21
   |
LL |         fn sub() -> Bar { 1 }
   |                     ^^^ not found in this scope
   |
note: type alias `a::b::Bar` exists but is inaccessible
  --> $DIR/issue-4366-2.rs:11:9
   |
LL |         type Bar = isize;
   |         ^^^^^^^^^^^^^^^^^ not accessible

error[E0423]: expected function, found module `foo`
  --> $DIR/issue-4366-2.rs:25:5
   |
LL |     foo();
   |     ^^^ not a function
   |
help: consider importing this function instead
   |
LL | use foo::foo;
   |

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0412, E0423.
For more information about an error, try `rustc --explain E0412`.
make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			error[E0412]: cannot find type `Bar` in this scope
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-4366-2.rs:15:21`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			`LL \| fn sub() -> Bar { 1 }`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\| ^^^ not found in this scope`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-23 22:20:58 -07:00			`\|`
Improve diagnostics for inaccessible items 2021-09-18 00:07:41 +02:00			note: type alias `a::b::Bar` exists but is inaccessible
			`--> $DIR/issue-4366-2.rs:11:9`
			`\|`
			`LL \| type Bar = isize;`
			`\| ^^^^^^^^^^^^^^^^^ not accessible`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			error[E0423]: expected function, found module `foo`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-4366-2.rs:25:5`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| foo();`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\| ^^^ not a function`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-23 22:20:58 -07:00			`\|`
Prefer accessible paths in 'use' suggestions This fixes an issue with the following sample: mod foo { mod inaccessible { pub struct X; } pub mod avail { pub struct X; } } fn main() { X; } Instead of suggesting both `use crate::foo::inaccessible::X;` and `use crate::foo::avail::X;`, it should only suggest the latter. It is done by trimming the list of suggestions from inaccessible paths if accessible paths are present. Visibility is checked with `is_accessible_from` now instead of being hard-coded. - Some tests fixes are trivial, and others require a bit more explaining, here are my comments: src/test/ui/issues/issue-35675.stderr: Only needs to make the enum public to have the suggestion make sense. src/test/ui/issues/issue-42944.stderr: Importing the tuple struct won't help because its constructor is not visible, so the attempted constructor does not work. In that case, it's better not to suggest it. The case where the constructor is public is covered in `issue-26545.rs`. 2020-06-13 20:58:46 +03:00			`help: consider importing this function instead`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
			`LL \| use foo::foo;`
			`\|`

			`error: aborting due to 2 previous errors`

hide `--explain` hint if error has no extended info 2019-04-17 13:26:38 -04:00			`Some errors have detailed explanations: E0412, E0423.`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			For more information about an error, try `rustc --explain E0412`.