rust/tests/ui/derives/deriving-no-inner-impl-error-message.rs

struct NoCloneOrEq;

#[derive(PartialEq)]
struct E {
    x: NoCloneOrEq //~ ERROR binary operation `==` cannot be applied to type `NoCloneOrEq`
}
#[derive(Clone)]
struct C {
    x: NoCloneOrEq
    //~^ ERROR `NoCloneOrEq: Clone` is not satisfied
}


fn main() {}
syntax: make deriving have slightly less cryptic error messages. This unfortunately changes an error like error: mismatched types: expected `&&NotClone` but found `&NotClone` into error: type `NotClone` does not implement any method in scope named `clone` 2014-01-28 00:20:50 +11:00			`struct NoCloneOrEq;`

Use `derive` rather than `deriving` in tests 2014-12-31 17:32:49 +13:00			`#[derive(PartialEq)]`
syntax: make deriving have slightly less cryptic error messages. This unfortunately changes an error like error: mismatched types: expected `&&NotClone` but found `&NotClone` into error: type `NotClone` does not implement any method in scope named `clone` 2014-01-28 00:20:50 +11:00			`struct E {`
Fix tests 2014-11-03 14:55:19 -05:00			x: NoCloneOrEq //~ ERROR binary operation `==` cannot be applied to type `NoCloneOrEq`
syntax: make deriving have slightly less cryptic error messages. This unfortunately changes an error like error: mismatched types: expected `&&NotClone` but found `&NotClone` into error: type `NotClone` does not implement any method in scope named `clone` 2014-01-28 00:20:50 +11:00			`}`
Use `derive` rather than `deriving` in tests 2014-12-31 17:32:49 +13:00			`#[derive(Clone)]`
syntax: make deriving have slightly less cryptic error messages. This unfortunately changes an error like error: mismatched types: expected `&&NotClone` but found `&NotClone` into error: type `NotClone` does not implement any method in scope named `clone` 2014-01-28 00:20:50 +11:00			`struct C {`
Fix error message in compile-fail test 2014-11-03 12:51:21 -05:00			`x: NoCloneOrEq`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			//~^ ERROR `NoCloneOrEq: Clone` is not satisfied
syntax: make deriving have slightly less cryptic error messages. This unfortunately changes an error like error: mismatched types: expected `&&NotClone` but found `&NotClone` into error: type `NotClone` does not implement any method in scope named `clone` 2014-01-28 00:20:50 +11:00			`}`


			`fn main() {}`