rust/src/test/ui/derives/deriving-bounds.rs

#[derive(Send)]
//~^ ERROR this unsafe trait should be implemented explicitly
struct Test;

#[derive(Sync)]
//~^ ERROR this unsafe trait should be implemented explicitly
struct Test1;

pub fn main() {}
Make #[derive(Anything)] into sugar for #[derive_Anything] This is a hack, but I don't think we can do much better as long as `derive` is running at the syntax expansion phase. If the custom_derive feature gate is enabled, this works with user-defined traits and syntax extensions. Without the gate, you can't use e.g. #[derive_Clone] directly, so this does not change the stable language. This commit also cleans up the deriving code somewhat, and forbids some previously-meaningless attribute syntax. For this reason it's technically a [breaking-change] 2015-03-06 15:15:54 -06:00			`#[derive(Send)]`
			`//~^ ERROR this unsafe trait should be implemented explicitly`
Allow built-in traits to be derived [RFC #3] cc #13231 2014-04-30 04:26:50 -05:00			`struct Test;`

Use `derive` rather than `deriving` in tests 2014-12-30 22:32:49 -06:00			`#[derive(Sync)]`
Make #[derive(Anything)] into sugar for #[derive_Anything] This is a hack, but I don't think we can do much better as long as `derive` is running at the syntax expansion phase. If the custom_derive feature gate is enabled, this works with user-defined traits and syntax extensions. Without the gate, you can't use e.g. #[derive_Clone] directly, so this does not change the stable language. This commit also cleans up the deriving code somewhat, and forbids some previously-meaningless attribute syntax. For this reason it's technically a [breaking-change] 2015-03-06 15:15:54 -06:00			`//~^ ERROR this unsafe trait should be implemented explicitly`
Keep track of the whole error chain 2014-12-23 03:57:44 -06:00			`struct Test1;`

Allow built-in traits to be derived [RFC #3] cc #13231 2014-04-30 04:26:50 -05:00			`pub fn main() {}`