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

error[E0425]: cannot find function `foo` in this scope
  --> $DIR/issue-4366.rs:18:29
   |
LL |         fn sub() -> isize { foo(); 1 }
   |                             ^^^ not found in this scope
   |
help: consider importing this function
   |
LL |         use foo::foo;
   |

error: aborting due to previous error

For more information about this error, try `rustc --explain E0425`.
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			error[E0425]: cannot find function `foo` in this scope
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-4366.rs:18:29`
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 \| fn sub() -> isize { foo(); 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			`\|`
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`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
			`LL \| use foo::foo;`
			`\|`

			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0425`.