rust/tests/ui/non-copyable-void.stderr

error[E0599]: no method named `clone` found for enum `c_void` in the current scope
  --> $DIR/non-copyable-void.rs:11:23
   |
LL |         let _z = (*y).clone();
   |                       ^^^^^ method not found in `c_void`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
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 02:40:56 -05:00			error[E0599]: no method named `clone` found for enum `c_void` in the current scope
tests: remove ignore directives from tests that mention core/alloc/std spans. 2020-03-31 20:10:13 -05:00			`--> $DIR/non-copyable-void.rs:11:23`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| let _z = (*y).clone();`
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 02:40:56 -05:00			\| ^^^^^ method not found in `c_void`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`

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