rust/tests/ui/resolve/use_suggestion_placement.stderr

error[E0412]: cannot find type `Path` in this scope
  --> $DIR/use_suggestion_placement.rs:18:16
   |
LL |     type Bar = Path;
   |                ^^^^ not found in this scope
   |
help: consider importing this struct
   |
LL |     use std::path::Path;
   |

error[E0425]: cannot find value `A` in this scope
  --> $DIR/use_suggestion_placement.rs:23:13
   |
LL |     let _ = A;
   |             ^ not found in this scope
   |
help: consider importing this constant
   |
LL | use m::A;
   |

error[E0412]: cannot find type `HashMap` in this scope
  --> $DIR/use_suggestion_placement.rs:28:23
   |
LL |     type Dict<K, V> = HashMap<K, V>;
   |                       ^^^^^^^ not found in this scope
   |
help: consider importing this struct
   |
LL | use std::collections::HashMap;
   |

error: aborting due to 3 previous errors

Some errors have detailed explanations: E0412, E0425.
For more information about an error, try `rustc --explain E0412`.
Add test for broken suggestion 2017-08-31 06:06:53 -05:00			error[E0412]: cannot find type `Path` in this scope
Update use_suggestion_placement.rs test, removing the FIXME that this PR fixes. (There is another issue, in that the fixed output is not ideally indented, but that is a pre-existing issue and should not block this PR.) 2022-03-04 16:14:34 -06:00			`--> $DIR/use_suggestion_placement.rs:18:16`
Add test for broken suggestion 2017-08-31 06:06:53 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| type Bar = Path;`
Add test for broken suggestion 2017-08-31 06:06:53 -05: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			`\|`
reword "possible candidate" import suggestion 2020-05-04 17:12:06 -05:00			`help: consider importing this struct`
Add test for broken suggestion 2017-08-31 06:06:53 -05:00			`\|`
Update UI tests 2018-02-24 17:01:39 -06:00			`LL \| use std::path::Path;`
Add test for broken suggestion 2017-08-31 06:06:53 -05:00			`\|`

Improve placement of `use` suggestions 2017-08-17 04:03:59 -05:00			error[E0425]: cannot find value `A` in this scope
Update use_suggestion_placement.rs test, removing the FIXME that this PR fixes. (There is another issue, in that the fixed output is not ideally indented, but that is a pre-existing issue and should not block this PR.) 2022-03-04 16:14:34 -06:00			`--> $DIR/use_suggestion_placement.rs:23:13`
Improve placement of `use` suggestions 2017-08-17 04:03:59 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| let _ = A;`
Improve placement of `use` suggestions 2017-08-17 04:03:59 -05: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			`\|`
reword "possible candidate" import suggestion 2020-05-04 17:12:06 -05:00			`help: consider importing this constant`
Improve placement of `use` suggestions 2017-08-17 04:03:59 -05:00			`\|`
Update UI tests 2018-02-24 17:01:39 -06:00			`LL \| use m::A;`
Improve placement of `use` suggestions 2017-08-17 04:03:59 -05:00			`\|`

			error[E0412]: cannot find type `HashMap` in this scope
Update use_suggestion_placement.rs test, removing the FIXME that this PR fixes. (There is another issue, in that the fixed output is not ideally indented, but that is a pre-existing issue and should not block this PR.) 2022-03-04 16:14:34 -06:00			`--> $DIR/use_suggestion_placement.rs:28:23`
Improve placement of `use` suggestions 2017-08-17 04:03:59 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| type Dict<K, V> = HashMap<K, V>;`
Improve placement of `use` suggestions 2017-08-17 04:03:59 -05: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			`\|`
Remove noisy suggestion of hash_map #72642 Fixed failing test-cases Remove noisy suggestion of hash_map #72642 Fixed failing test-cases 2020-06-05 04:57:37 -05:00			`help: consider importing this struct`
Improve placement of `use` suggestions 2017-08-17 04:03:59 -05:00			`\|`
Update UI tests 2018-02-24 17:01:39 -06:00			`LL \| use std::collections::HashMap;`
Improve placement of `use` suggestions 2017-08-17 04:03:59 -05:00			`\|`

Add new error comparision to hide desugaring First some background: To the compiler, the following two signatures in the trait vs the impl are the same. ```rust trait Foo { fn foo(&self, &impl Debug); } impl Foo for () { fn foo<U: Debug>(&self, x: &U) { ... } } ``` We do not want to allow this, and so we add a new error and check. The check just tests that all paramters 'syntheticness' match up. As during collection, the impl Trait parameters are transformed into anonymous synthetic generics. Furthermore, causes a check for unused type parameters to be skipped in check_bounds_are_used if there is already a TyError. Thus, an unused input will not trigger `type parameter unused` errors. Update the one test that checked for this error in the case of a TyError. 2017-11-10 11:47:33 -06:00			`error: aborting due to 3 previous errors`
Improve placement of `use` suggestions 2017-08-17 04:03:59 -05:00
hide `--explain` hint if error has no extended info 2019-04-17 12:26:38 -05:00			`Some errors have detailed explanations: E0412, E0425.`
update tests 2018-03-03 08:59:40 -06:00			For more information about an error, try `rustc --explain E0412`.