rust/src/test/ui/span/gated-features-attr-spans.stderr

error[E0658]: SIMD types are experimental and possibly buggy (see issue #27731)
  --> $DIR/gated-features-attr-spans.rs:20:1
   |
20 | #[repr(simd)] //~ ERROR are experimental
   | ^^^^^^^^^^^^^
   |
   = help: add #![feature(repr_simd)] to the crate attributes to enable

warning: `#[must_use]` on methods is experimental (see issue #43302)
  --> $DIR/gated-features-attr-spans.rs:27:5
   |
27 |     #[must_use] fn summon_weapon(&self) -> Weapon { self.weapon }
   |     ^^^^^^^^^^^
   |
   = help: add #![feature(fn_must_use)] to the crate attributes to enable

warning: `#[must_use]` on functions is experimental (see issue #43302)
  --> $DIR/gated-features-attr-spans.rs:31:1
   |
31 | #[must_use] //~ WARN is experimental
   | ^^^^^^^^^^^
   |
   = help: add #![feature(fn_must_use)] to the crate attributes to enable

error: aborting due to previous error
Add error code for unstable feature errors 2018-01-13 07:05:51 -06:00			`error[E0658]: SIMD types are experimental and possibly buggy (see issue #27731)`
feature error span on attr. for fn_must_use, SIMD/align, macro reëxport There were several feature-gated attributes for which the feature-not-available error spans would point to the item annotated with the gated attribute, when it would make more sense for the span to point to the attribute itself: if the attribute is removed, the function/struct/&c. likely still makes sense and the program will compile. (Note that we decline to make the analogous change for the `main`, `start`, and `plugin_registrar` features, for in those cases it makes sense for the span to implicate the entire function, of which there is little hope of using without the gated attribute.) 2017-08-26 20:00:33 -05:00			`--> $DIR/gated-features-attr-spans.rs:20:1`
			`\|`
Merge cfail and ui tests into ui tests 2017-11-20 06:13:27 -06:00			`20 \| #[repr(simd)] //~ ERROR are experimental`
feature error span on attr. for fn_must_use, SIMD/align, macro reëxport There were several feature-gated attributes for which the feature-not-available error spans would point to the item annotated with the gated attribute, when it would make more sense for the span to point to the attribute itself: if the attribute is removed, the function/struct/&c. likely still makes sense and the program will compile. (Note that we decline to make the analogous change for the `main`, `start`, and `plugin_registrar` features, for in those cases it makes sense for the span to implicate the entire function, of which there is little hope of using without the gated attribute.) 2017-08-26 20:00:33 -05:00			`\| ^^^^^^^^^^^^^`
			`\|`
			`= help: add #![feature(repr_simd)] to the crate attributes to enable`

			warning: `#[must_use]` on methods is experimental (see issue #43302)
			`--> $DIR/gated-features-attr-spans.rs:27:5`
			`\|`
			`27 \| #[must_use] fn summon_weapon(&self) -> Weapon { self.weapon }`
			`\| ^^^^^^^^^^^`
			`\|`
			`= help: add #![feature(fn_must_use)] to the crate attributes to enable`

			warning: `#[must_use]` on functions is experimental (see issue #43302)
Merge cfail and ui tests into ui tests 2017-11-20 06:13:27 -06:00			`--> $DIR/gated-features-attr-spans.rs:31:1`
feature error span on attr. for fn_must_use, SIMD/align, macro reëxport There were several feature-gated attributes for which the feature-not-available error spans would point to the item annotated with the gated attribute, when it would make more sense for the span to point to the attribute itself: if the attribute is removed, the function/struct/&c. likely still makes sense and the program will compile. (Note that we decline to make the analogous change for the `main`, `start`, and `plugin_registrar` features, for in those cases it makes sense for the span to implicate the entire function, of which there is little hope of using without the gated attribute.) 2017-08-26 20:00:33 -05:00			`\|`
Merge cfail and ui tests into ui tests 2017-11-20 06:13:27 -06:00			`31 \| #[must_use] //~ WARN is experimental`
feature error span on attr. for fn_must_use, SIMD/align, macro reëxport There were several feature-gated attributes for which the feature-not-available error spans would point to the item annotated with the gated attribute, when it would make more sense for the span to point to the attribute itself: if the attribute is removed, the function/struct/&c. likely still makes sense and the program will compile. (Note that we decline to make the analogous change for the `main`, `start`, and `plugin_registrar` features, for in those cases it makes sense for the span to implicate the entire function, of which there is little hope of using without the gated attribute.) 2017-08-26 20:00:33 -05:00			`\| ^^^^^^^^^^^`
			`\|`
			`= help: add #![feature(fn_must_use)] to the crate attributes to enable`

Stabilized `#[repr(align(x))]` attribute (RFC 1358) 2017-12-25 17:24:23 -06:00			`error: aborting due to previous error`
feature error span on attr. for fn_must_use, SIMD/align, macro reëxport There were several feature-gated attributes for which the feature-not-available error spans would point to the item annotated with the gated attribute, when it would make more sense for the span to point to the attribute itself: if the attribute is removed, the function/struct/&c. likely still makes sense and the program will compile. (Note that we decline to make the analogous change for the `main`, `start`, and `plugin_registrar` features, for in those cases it makes sense for the span to implicate the entire function, of which there is little hope of using without the gated attribute.) 2017-08-26 20:00:33 -05:00