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:11:1
   |
LL | #[repr(simd)] //~ ERROR are experimental
   | ^^^^^^^^^^^^^
   |
   = help: add #![feature(repr_simd)] to the crate attributes to enable

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
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)`
stabilize `#[must_use]` for functions and must-use operators This is in the matter of RFC 1940 and tracking issue #43302. 2018-03-10 18:23:28 -06:00			`--> $DIR/gated-features-attr-spans.rs:11: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			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| #[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`

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
update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0658`.