rust/tests/ui/derives/derives-span-PartialOrd-struct.rs

// This file was auto-generated using 'src/etc/generate-deriving-span-tests.py'

#[derive(PartialEq)]
struct Error;

#[derive(PartialOrd,PartialEq)]
struct Struct {
    x: Error //~ ERROR can't compare `Error` with `Error`
}

fn main() {}
std: Rename {Eq,Ord} to Partial{Eq,Ord} This is part of the ongoing renaming of the equality traits. See #12517 for more details. All code using Eq/Ord will temporarily need to move to Partial{Eq,Ord} or the Total{Eq,Ord} traits. The Total traits will soon be renamed to {Eq,Ord}. cc #12517 [breaking-change] 2014-05-29 19:45:07 -05:00			`// This file was auto-generated using 'src/etc/generate-deriving-span-tests.py'`
Add autogenerated tests for the spans of various derived traits. 2014-01-26 22:28:04 -06:00
Use `derive` rather than `deriving` in tests 2014-12-30 22:32:49 -06:00			`#[derive(PartialEq)]`
Add autogenerated tests for the spans of various derived traits. 2014-01-26 22:28:04 -06:00			`struct Error;`
syntax::ext: Make type errors in deriving point to the field itself. This rearranges the deriving code so that #[deriving] a trait on a field that doesn't implement that trait will point to the field in question, e.g. struct NotEq; // doesn't implement Eq #[deriving(Eq)] struct Foo { ok: int, also_ok: ~str, bad: NotEq // error points here. } Unfortunately, this means the error is disconnected from the `deriving` itself but there's no current way to pass that information through to rustc except via the spans, at the moment. Fixes #7724. 2013-11-07 01:49:01 -06:00
Use `derive` rather than `deriving` in tests 2014-12-30 22:32:49 -06:00			`#[derive(PartialOrd,PartialEq)]`
Add autogenerated tests for the spans of various derived traits. 2014-01-26 22:28:04 -06:00			`struct Struct {`
Update tests 2020-01-08 11:02:10 -06:00			x: Error //~ ERROR can't compare `Error` with `Error`
syntax::ext: Make type errors in deriving point to the field itself. This rearranges the deriving code so that #[deriving] a trait on a field that doesn't implement that trait will point to the field in question, e.g. struct NotEq; // doesn't implement Eq #[deriving(Eq)] struct Foo { ok: int, also_ok: ~str, bad: NotEq // error points here. } Unfortunately, this means the error is disconnected from the `deriving` itself but there's no current way to pass that information through to rustc except via the spans, at the moment. Fixes #7724. 2013-11-07 01:49:01 -06:00			`}`

Add autogenerated tests for the spans of various derived traits. 2014-01-26 22:28:04 -06:00			`fn main() {}`