rust/tests/ui/reachable/issue-11225-2.rs

// run-pass
// aux-build:issue-11225-2.rs

// pretty-expanded FIXME #23616

extern crate issue_11225_2 as foo;

pub fn main() {
    foo::foo(1);
    foo::foo_ufcs(1);
}
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 07:18:55 -05:00			`// run-pass`
Conservatively export all trait methods and impls The comments have more information as to why this is done, but the basic idea is that finding an exported trait is actually a fairly difficult problem. The true answer lies in whether a trait is ever referenced from another exported method, and right now this kind of analysis doesn't exist, so the conservative answer of "yes" is always returned to answer whether a trait is exported. Closes #11224 Closes #11225 2013-12-31 14:40:10 -06:00			`// aux-build:issue-11225-2.rs`

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 15:13:15 -05:00			`// pretty-expanded FIXME #23616`

Fix fallout of removing quotes in crate names 2015-03-27 12:22:44 -05:00			`extern crate issue_11225_2 as foo;`
Conservatively export all trait methods and impls The comments have more information as to why this is done, but the basic idea is that finding an exported trait is actually a fairly difficult problem. The true answer lies in whether a trait is ever referenced from another exported method, and right now this kind of analysis doesn't exist, so the conservative answer of "yes" is always returned to answer whether a trait is exported. Closes #11224 Closes #11225 2013-12-31 14:40:10 -06:00
test: Make all the run-pass tests use `pub fn main` 2014-01-03 17:30:54 -06:00			`pub fn main() {`
Remove all `i` suffixes 2015-01-25 15:05:03 -06:00			`foo::foo(1);`
rustc_privacy: Do not export items needed solely for the reachability analysis Process them in middle::reachable instead Add tests for reachability of trait methods written in UFCS form 2015-11-05 09:17:33 -06:00			`foo::foo_ufcs(1);`
Conservatively export all trait methods and impls The comments have more information as to why this is done, but the basic idea is that finding an exported trait is actually a fairly difficult problem. The true answer lies in whether a trait is ever referenced from another exported method, and right now this kind of analysis doesn't exist, so the conservative answer of "yes" is always returned to answer whether a trait is exported. Closes #11224 Closes #11225 2013-12-31 14:40:10 -06:00			`}`