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

error[E0308]: mismatched types
  --> $DIR/issue-13446.rs:3:26
   |
LL | static VEC: [u32; 256] = vec![];
   |                          ^^^^^^ expected `[u32; 256]`, found `Vec<_>`
   |
   = note: expected array `[u32; 256]`
             found struct `Vec<_>`
   = note: this error originates in the macro `vec` (in Nightly builds, run with -Z macro-backtrace for more info)

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 16:11:54 -05:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-13446.rs:3:26`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
			`LL \| static VEC: [u32; 256] = vec![];`
Modify primary span label for E0308 The previous output was unintuitive to users. 2023-01-02 20:00:33 -06:00			\| ^^^^^^ expected `[u32; 256]`, found `Vec<_>`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
Specific labels when referring to "expected" and "found" types 2019-11-13 16:16:56 -06:00			= note: expected array `[u32; 256]`
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			found struct `Vec<_>`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 13:52:25 -06:00			= note: this error originates in the macro `vec` (in Nightly builds, run with -Z macro-backtrace for more info)
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			`error: aborting due to previous error`

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