rust/tests/ui/duplicate_entry_error.stderr

error[E0152]: found duplicate lang item `panic_impl`
  --> $DIR/duplicate_entry_error.rs:11:1
   |
LL | fn panic_impl(info: &PanicInfo) -> ! {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: the lang item is first defined in crate `std` (which `duplicate_entry_error` depends on)
   = note: first definition in `std` loaded from SYSROOT/libstd-*.rlib
   = note: second definition in the local crate (`duplicate_entry_error`)

error: aborting due to previous error

For more information about this error, try `rustc --explain E0152`.
Diagnostics should not end with a full stop 2020-01-10 14:36:22 +00:00			error[E0152]: found duplicate lang item `panic_impl`
Provide more information on duplicate lang item error. 2020-06-17 18:05:30 +00:00			`--> $DIR/duplicate_entry_error.rs:11:1`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
Use smaller def span for functions Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata. 2020-08-12 21:02:14 +00:00			`LL \| fn panic_impl(info: &PanicInfo) -> ! {`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
Normalise notes with the/is 2020-01-22 23:57:38 +00:00			= note: the lang item is first defined in crate `std` (which `duplicate_entry_error` depends on)
Provide more information on duplicate lang item error. 2020-06-17 18:05:30 +00:00			= note: first definition in `std` loaded from SYSROOT/libstd-*.rlib
Switch crate_extern_paths to a query, and tweak wording. 2020-06-27 21:54:19 +00:00			= note: second definition in the local crate (`duplicate_entry_error`)
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
			`error: aborting due to previous error`

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