This website requires JavaScript.
Explore
Help
Register
Sign In
mikros
/
rust
Watch
1
Star
0
Fork
0
You've already forked rust
Code
Issues
Pull Requests
Packages
Projects
Releases
Wiki
Activity
c60a6b93fb
rust
/
src
/
test
/
compile-fail
/
bad-module.rs
5 lines
92 B
Rust
Raw
Normal View
History
Unescape
Escape
Be less specific in 'unresolved import' error patterns To make sure different test set-ups (check-fast) don't cause the tests to fail.
2011-12-02 10:20:03 -06:00
// error-pattern: unresolved import
Copy first batch of material from libstd to libcore.
2011-12-13 18:25:51 -06:00
import
thing
;
Improve nonexistent-module error message The error message for (for example) "import vec;" without "use std;" was "cyclic import", which was misleading because there were no cycles. I changed it to "cyclic import or nonexistent module", which doesn't break existing tests.
2011-05-24 12:46:48 -05:00
Switch the compiler over to using ~[] notation instead of []/~. Closes #2759.
2012-06-29 18:26:56 -05:00
fn
main
(
)
{
let
foo
=
thing
::
len
(
~
[
]
)
;
}
Reference in New Issue
Copy Permalink