rust/tests/ui/copy-a-resource.stderr

error[E0599]: no method named `clone` found for struct `Foo` in the current scope
  --> $DIR/copy-a-resource.rs:18:16
   |
LL | struct Foo {
   | ---------- method `clone` not found for this struct
...
LL |     let _y = x.clone();
   |                ^^^^^ method not found in `Foo`
   |
   = help: items from traits can only be used if the trait is implemented and in scope
   = note: the following trait defines an item `clone`, perhaps you need to implement it:
           candidate #1: `Clone`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0599`.
Unify output of "variant not found" errors 2020-01-08 16:05:31 +00:00			error[E0599]: no method named `clone` found for struct `Foo` in the current scope
tests: remove ignore directives from tests that mention core/alloc/std spans. 2020-04-01 01:10:13 +00:00			`--> $DIR/copy-a-resource.rs:18:16`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
make non_camel_case_types an early lint 2018-12-17 03:21:47 +00:00			`LL \| struct Foo {`
Track implicit `Sized` obligations in type params Suggest adding a `?Sized` bound if appropriate on E0599 by inspecting the HIR Generics. (Fix #98539) 2022-07-01 23:47:26 +00:00			\| ---------- method `clone` not found for this struct
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`...`
			`LL \| let _y = x.clone();`
Give method not found a primary span label 2019-09-06 19:00:07 +00:00			\| ^^^^^ method not found in `Foo`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
			`= help: items from traits can only be used if the trait is implemented and in scope`
			= note: the following trait defines an item `clone`, perhaps you need to implement it:
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			candidate #1: `Clone`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
			For more information about this error, try `rustc --explain E0599`.