rust/src/test/ui/issues/issue-42944.stderr

error[E0423]: expected function, found struct `B`
  --> $DIR/issue-42944.rs:9:9
   |
LL |         B(());
   |         ^ constructor is not visible here due to private fields

error[E0425]: cannot find function `B` in this scope
  --> $DIR/issue-42944.rs:15:9
   |
LL |         B(());
   |         ^ not found in this scope
   |
help: possible candidate is found in another module, you can import it into scope
   |
LL |     use foo::B;
   |

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0423, E0425.
For more information about an error, try `rustc --explain E0423`.
Only suggest imports if not imported. This commit modifies name resolution error reporting so that if a name is in scope and has been imported then we do not suggest importing it. This can occur when we add a label about constructors not being visible due to private fields. In these cases, we know that the struct/variant has been imported and we should silence any suggestions to import the struct/variant. 2019-02-11 12:29:10 -06:00			error[E0423]: expected function, found struct `B`
			`--> $DIR/issue-42944.rs:9:9`
			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| B(());`
Only suggest imports if not imported. This commit modifies name resolution error reporting so that if a name is in scope and has been imported then we do not suggest importing it. This can occur when we add a label about constructors not being visible due to private fields. In these cases, we know that the struct/variant has been imported and we should silence any suggestions to import the struct/variant. 2019-02-11 12:29:10 -06:00			`\| ^ constructor is not visible here due to private fields`

			error[E0425]: cannot find function `B` in this scope
			`--> $DIR/issue-42944.rs:15:9`
			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| B(());`
Only suggest imports if not imported. This commit modifies name resolution error reporting so that if a name is in scope and has been imported then we do not suggest importing it. This can occur when we add a label about constructors not being visible due to private fields. In these cases, we know that the struct/variant has been imported and we should silence any suggestions to import the struct/variant. 2019-02-11 12:29:10 -06: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-24 00:20:58 -05:00			`\|`
Only suggest imports if not imported. This commit modifies name resolution error reporting so that if a name is in scope and has been imported then we do not suggest importing it. This can occur when we add a label about constructors not being visible due to private fields. In these cases, we know that the struct/variant has been imported and we should silence any suggestions to import the struct/variant. 2019-02-11 12:29:10 -06:00			`help: possible candidate is found in another module, you can import it into scope`
			`\|`
			`LL \| use foo::B;`
			`\|`

			`error: aborting due to 2 previous errors`

hide `--explain` hint if error has no extended info 2019-04-17 12:26:38 -05:00			`Some errors have detailed explanations: E0423, E0425.`
Only suggest imports if not imported. This commit modifies name resolution error reporting so that if a name is in scope and has been imported then we do not suggest importing it. This can occur when we add a label about constructors not being visible due to private fields. In these cases, we know that the struct/variant has been imported and we should silence any suggestions to import the struct/variant. 2019-02-11 12:29:10 -06:00			For more information about an error, try `rustc --explain E0423`.