rust/tests/ui/impl-not-adjacent-to-type.rs

//@ run-pass

mod foo {
    pub struct Point {
        pub x: i32,
        #[allow(dead_code)]
        pub y: i32,
    }
}

impl foo::Point {
    fn x(&self) -> i32 { self.x }
}

fn main() {
    assert_eq!((foo::Point { x: 1, y: 3}).x(), 1);
}
tests: Add missing run-pass annotations 2019-07-27 05:54:25 +08:00			`//@ run-pass`

librustc: Forbid inherent implementations that aren't adjacent to the type they provide an implementation for. This breaks code like: mod foo { struct Foo { ... } } impl foo::Foo { ... } Change this code to: mod foo { struct Foo { ... } impl Foo { ... } } Additionally, if you used the I/O path extension methods `stat`, `lstat`, `exists`, `is_file`, or `is_dir`, note that these methods have been moved to the the `std::io::fs::PathExtensions` trait. This breaks code like: fn is_it_there() -> bool { Path::new("/foo/bar/baz").exists() } Change this code to: use std::io::fs::PathExtensions; fn is_it_there() -> bool { Path::new("/foo/bar/baz").exists() } Closes #17059. RFC #155. [breaking-change] 2014-09-11 13:26:41 +08:00			`mod foo {`
rustc_resolve: don't handle impl items as if they were modules. 2015-02-20 14:17:05 +08:00			`pub struct Point {`
			`pub x: i32,`
Allow unused fields in some tests The dead_code lint was previously eroneously missing those. Since this lint bug has been fixed, the unused fields warnings need to be fixed. Most of them are marked as `#[allow(dead_code)]`. Other warnings are fixed by changing visibility of modules. 2024-02-21 04:20:14 +08:00			`#[allow(dead_code)]`
rustc_resolve: don't handle impl items as if they were modules. 2015-02-20 14:17:05 +08:00			`pub y: i32,`
librustc: Forbid inherent implementations that aren't adjacent to the type they provide an implementation for. This breaks code like: mod foo { struct Foo { ... } } impl foo::Foo { ... } Change this code to: mod foo { struct Foo { ... } impl Foo { ... } } Additionally, if you used the I/O path extension methods `stat`, `lstat`, `exists`, `is_file`, or `is_dir`, note that these methods have been moved to the the `std::io::fs::PathExtensions` trait. This breaks code like: fn is_it_there() -> bool { Path::new("/foo/bar/baz").exists() } Change this code to: use std::io::fs::PathExtensions; fn is_it_there() -> bool { Path::new("/foo/bar/baz").exists() } Closes #17059. RFC #155. [breaking-change] 2014-09-11 13:26:41 +08:00			`}`
			`}`

rustc_resolve: don't handle impl items as if they were modules. 2015-02-20 14:17:05 +08:00			`impl foo::Point {`
			`fn x(&self) -> i32 { self.x }`
librustc: Forbid inherent implementations that aren't adjacent to the type they provide an implementation for. This breaks code like: mod foo { struct Foo { ... } } impl foo::Foo { ... } Change this code to: mod foo { struct Foo { ... } impl Foo { ... } } Additionally, if you used the I/O path extension methods `stat`, `lstat`, `exists`, `is_file`, or `is_dir`, note that these methods have been moved to the the `std::io::fs::PathExtensions` trait. This breaks code like: fn is_it_there() -> bool { Path::new("/foo/bar/baz").exists() } Change this code to: use std::io::fs::PathExtensions; fn is_it_there() -> bool { Path::new("/foo/bar/baz").exists() } Closes #17059. RFC #155. [breaking-change] 2014-09-11 13:26:41 +08:00			`}`

rustc_resolve: don't handle impl items as if they were modules. 2015-02-20 14:17:05 +08:00			`fn main() {`
			`assert_eq!((foo::Point { x: 1, y: 3}).x(), 1);`
			`}`