rust/tests/ui/marker_trait_attr/marker-trait-with-associated-items.stderr

error[E0714]: marker traits cannot have associated items
  --> $DIR/marker-trait-with-associated-items.rs:6:5
   |
LL |     const N: usize;
   |     ^^^^^^^^^^^^^^

error[E0714]: marker traits cannot have associated items
  --> $DIR/marker-trait-with-associated-items.rs:12:5
   |
LL |     type Output;
   |     ^^^^^^^^^^^

error[E0714]: marker traits cannot have associated items
  --> $DIR/marker-trait-with-associated-items.rs:18:5
   |
LL |     fn foo();
   |     ^^^^^^^^^

error[E0714]: marker traits cannot have associated items
  --> $DIR/marker-trait-with-associated-items.rs:24:5
   |
LL |     const N: usize = 43;
   |     ^^^^^^^^^^^^^^

error[E0714]: marker traits cannot have associated items
  --> $DIR/marker-trait-with-associated-items.rs:30:5
   |
LL |     type Output = ();
   |     ^^^^^^^^^^^

error[E0714]: marker traits cannot have associated items
  --> $DIR/marker-trait-with-associated-items.rs:36:5
   |
LL |     fn foo() {}
   |     ^^^^^^^^

error: aborting due to 6 previous errors

For more information about this error, try `rustc --explain E0714`.
Improve error checking and reporting - Check for valid attributes more reliably - Don't bloat the error index for boring errors - Do use real error codes for the interesting ones 2018-09-03 04:17:20 -05:00			`error[E0714]: marker traits cannot have associated items`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/marker-trait-with-associated-items.rs:6:5`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00			`\|`
			`LL \| const N: usize;`
Shorten def_span for more items. 2022-02-13 09:27:59 -06:00			`\| ^^^^^^^^^^^^^^`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00
Improve error checking and reporting - Check for valid attributes more reliably - Don't bloat the error index for boring errors - Do use real error codes for the interesting ones 2018-09-03 04:17:20 -05:00			`error[E0714]: marker traits cannot have associated items`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/marker-trait-with-associated-items.rs:12:5`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00			`\|`
			`LL \| type Output;`
Shorten def_span for more items. 2022-02-13 09:27:59 -06:00			`\| ^^^^^^^^^^^`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00
Improve error checking and reporting - Check for valid attributes more reliably - Don't bloat the error index for boring errors - Do use real error codes for the interesting ones 2018-09-03 04:17:20 -05:00			`error[E0714]: marker traits cannot have associated items`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/marker-trait-with-associated-items.rs:18:5`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00			`\|`
			`LL \| fn foo();`
			`\| ^^^^^^^^^`

Improve error checking and reporting - Check for valid attributes more reliably - Don't bloat the error index for boring errors - Do use real error codes for the interesting ones 2018-09-03 04:17:20 -05:00			`error[E0714]: marker traits cannot have associated items`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/marker-trait-with-associated-items.rs:24:5`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00			`\|`
			`LL \| const N: usize = 43;`
Shorten def_span for more items. 2022-02-13 09:27:59 -06:00			`\| ^^^^^^^^^^^^^^`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00
Improve error checking and reporting - Check for valid attributes more reliably - Don't bloat the error index for boring errors - Do use real error codes for the interesting ones 2018-09-03 04:17:20 -05:00			`error[E0714]: marker traits cannot have associated items`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/marker-trait-with-associated-items.rs:30:5`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00			`\|`
			`LL \| type Output = ();`
Shorten def_span for more items. 2022-02-13 09:27:59 -06:00			`\| ^^^^^^^^^^^`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00
Improve error checking and reporting - Check for valid attributes more reliably - Don't bloat the error index for boring errors - Do use real error codes for the interesting ones 2018-09-03 04:17:20 -05:00			`error[E0714]: marker traits cannot have associated items`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/marker-trait-with-associated-items.rs:36:5`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00			`\|`
			`LL \| fn foo() {}`
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 16:02:14 -05:00			`\| ^^^^^^^^`
Enforce that #[marker] traits cannot have associated items 2018-09-03 03:36:01 -05:00
			`error: aborting due to 6 previous errors`

Improve error checking and reporting - Check for valid attributes more reliably - Don't bloat the error index for boring errors - Do use real error codes for the interesting ones 2018-09-03 04:17:20 -05:00			For more information about this error, try `rustc --explain E0714`.