rust/tests/ui/issues/issue-2526-a.rs

//@ run-pass
//@ aux-build:issue-2526.rs

//@ pretty-expanded FIXME #23616

#![allow(unused_imports)]

extern crate issue_2526;
use issue_2526::*;

pub 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 12:18:55 +00:00			`//@ run-pass`
Traverse types in reachability Issue 2526 showed a test case where a library exported only a type that was a synonym for a class. Because the class's destructor wasn't getting marked as reachable, its linkage was wrongly getting set to "internal". The solution is for reachability to traverse types. Closes #2526. 2012-06-13 18:20:21 +00:00			`//@ aux-build:issue-2526.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 20:13:15 +00:00			`//@ pretty-expanded FIXME #23616`

Use new attribute syntax in python files in src/etc too (#13478) 2014-04-14 15:30:31 +00:00			`#![allow(unused_imports)]`
Fix warnings it tests 2013-08-17 15:37:42 +00:00
extern mod => extern crate This was previously implemented, and it just needed a snapshot to go through 2014-02-14 18:10:06 +00:00			`extern crate issue_2526;`
test: "import" -> "use" 2012-09-05 19:32:05 +00:00			`use issue_2526::*;`
Traverse types in reachability Issue 2526 showed a test case where a library exported only a type that was a synonym for a class. Because the class's destructor wasn't getting marked as reachable, its linkage was wrongly getting set to "internal". The solution is for reachability to traverse types. Closes #2526. 2012-06-13 18:20:21 +00:00
check-fast fallout from removing export, r=burningtree 2013-02-02 03:43:17 +00:00			`pub fn main() {}`