rust/tests/ui/issues/issue-40749.stderr

error[E0308]: mismatched types
  --> $DIR/issue-40749.rs:2:9
   |
LL |     [0; ..10];
   |         ^^^^ expected `usize`, found `RangeTo<{integer}>`
   |
   = note: expected type `usize`
            found struct `RangeTo<{integer}>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-40749.rs:2:9`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
			`LL \| [0; ..10];`
Modify primary span label for E0308 The previous output was unintuitive to users. 2023-01-03 02:00:33 +00:00			\| ^^^^ expected `usize`, found `RangeTo<{integer}>`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
			= note: expected type `usize`
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			found struct `RangeTo<{integer}>`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			`error: aborting due to previous error`

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