os-rust/tests/ui/traits/impl-2.rs

// run-pass
#![allow(dead_code)]
#![allow(non_snake_case)]

// pretty-expanded FIXME #23616

pub mod Foo {
    pub trait Trait {
        fn foo(&self);
    }
}

mod Bar {
    impl<'a> dyn (::Foo::Trait) + 'a {
        fn bar(&self) { self.foo() }
    }
}

fn main() {}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 14:18:55 +02:00			`// run-pass`
Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling with clean stderr again. Most were added mechanically. 2018-09-25 23:51:35 +02:00			`#![allow(dead_code)]`
Add `#![allow(..)]` for a slew of lints of migrated run-pass tests, to silence stderr output. 2018-08-31 15:02:01 +02:00			`#![allow(non_snake_case)]`

rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 13:13:15 -07:00			`// pretty-expanded FIXME #23616`

Fix fallout from allowing impls outside of the type's definition module. 2015-02-20 11:36:31 +02:00			`pub mod Foo {`
			`pub trait Trait {`
rustc_resolve: don't handle impl items as if they were modules. 2015-02-20 08:17:05 +02:00			`fn foo(&self);`
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-10 22:26:41 -07:00			`}`
			`}`

rustc_resolve: don't handle impl items as if they were modules. 2015-02-20 08:17:05 +02:00			`mod Bar {`
Update run-pass test suite to use dyn 2019-05-28 14:47:21 -04:00			`impl<'a> dyn (::Foo::Trait) + 'a {`
rustc_resolve: don't handle impl items as if they were modules. 2015-02-20 08:17:05 +02:00			`fn bar(&self) { self.foo() }`
			`}`
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-10 22:26:41 -07:00			`}`

			`fn main() {}`