rust/tests/ui/binop/binop-bitxor-str.stderr

error[E0369]: no implementation for `String ^ String`
  --> $DIR/binop-bitxor-str.rs:3:37
   |
LL | fn main() { let x = "a".to_string() ^ "b".to_string(); }
   |                     --------------- ^ --------------- String
   |                     |
   |                     String

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0369`.
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[E0369]: no implementation for `String ^ String`
Better diagnostic for binary operation on BoxedValues 2019-03-27 12:13:09 -05:00			`--> $DIR/binop-bitxor-str.rs:3:37`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| fn main() { let x = "a".to_string() ^ "b".to_string(); }`
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			`\| --------------- ^ --------------- String`
Better diagnostic for binary operation on BoxedValues 2019-03-27 12:13:09 -05:00			`\| \|`
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			`\| String`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			For more information about this error, try `rustc --explain E0369`.