rust/src/test/compile-fail/import4.rs

// error-pattern: cyclic import

mod a { import foo = b::foo; export foo; }
mod b { import foo = a::foo; export foo; }

fn main(args: ~[str]) { #debug("loop"); }
Revert "rustc: Switch to the new resolution pass" This reverts commit c4af6e92fbae171c56a4e68666025725555fc9d8. Branch was burning...many, many unresolved imports. 2012-07-06 22:45:06 -05:00			`// error-pattern: cyclic import`
Fix the import handling in "complex" cases. When looking a.b.c and 'a' is a module, we should look for 'b' just in the module 'a' and then continue resolving b.c in the environment created by updating with a. Still not 100% correct, but getting there. 2011-01-14 16:20:14 -06:00
Make import ignore imports coming after them This broke no code at all, so I guess people were already writing imports in this style. Issue #1228 2011-12-02 09:06:55 -06:00			`mod a { import foo = b::foo; export foo; }`
			`mod b { import foo = a::foo; export foo; }`
Fix the import handling in "complex" cases. When looking a.b.c and 'a' is a module, we should look for 'b' just in the module 'a' and then continue resolving b.c in the environment created by updating with a. Still not 100% correct, but getting there. 2011-01-14 16:20:14 -06:00
Switch the compiler over to using ~[] notation instead of []/~. Closes #2759. 2012-06-29 18:26:56 -05:00			`fn main(args: ~[str]) { #debug("loop"); }`