rust/src/test/auxiliary/issue_2316_b.rs

extern mod issue_2316_a;

mod cloth {
    #[legacy_exports];

use issue_2316_a::*;

export calico, gingham, flannel;
export fabric;

enum fabric {
  gingham, flannel, calico
}

}
Convert 'use' to 'extern mod'. Remove old 'use' syntax 2012-09-11 19:46:20 -05:00			`extern mod issue_2316_a;`
Don't re-export a glob-imported ID when the same ID is defined within a module See the test case I added (issue-2316-c) for a concrete example. issue-2316 also contains the originally reported test case. resolve was using bitwise or instead of logical or when checking exports, resulting in excessively eager evaluation. A one-line fix that took six hours to isolate ;-) 2012-05-01 01:26:21 -05:00
			`mod cloth {`
Install new pub/priv/export rules as defaults, old rules accessible under #[legacy_exports]; 2012-09-21 20:10:45 -05:00			`#[legacy_exports];`
Don't re-export a glob-imported ID when the same ID is defined within a module See the test case I added (issue-2316-c) for a concrete example. issue-2316 also contains the originally reported test case. resolve was using bitwise or instead of logical or when checking exports, resulting in excessively eager evaluation. A one-line fix that took six hours to isolate ;-) 2012-05-01 01:26:21 -05:00
test: "import" -> "use" 2012-09-05 14:32:05 -05:00			`use issue_2316_a::*;`
Don't re-export a glob-imported ID when the same ID is defined within a module See the test case I added (issue-2316-c) for a concrete example. issue-2316 also contains the originally reported test case. resolve was using bitwise or instead of logical or when checking exports, resulting in excessively eager evaluation. A one-line fix that took six hours to isolate ;-) 2012-05-01 01:26:21 -05:00
			`export calico, gingham, flannel;`
			`export fabric;`

			`enum fabric {`
			`gingham, flannel, calico`
			`}`

			`}`