| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2018-07-15 | Move some `compile-fail` tests to `ui` | Esteban Küber | -16/+0 | |
| 2017-07-25 | Point at path segment on module not found | Esteban Küber | -1/+1 | |
| Point at the correct path segment on a import statement where a module doesn't exist. New output: ```rust error[E0432]: unresolved import `std::bar` --> <anon>:1:10 | 1 | use std::bar::{foo1, foo2}; | ^^^ Could not find `bar` in `std` ``` instead of: ```rust error[E0432]: unresolved import `std::bar::foo1` --> <anon>:1:16 | 1 | use std::bar::{foo1, foo2}; | ^^^^ Could not find `bar` in `std` error[E0432]: unresolved import `std::bar::foo2` --> <anon>:1:22 | 1 | use std::bar::{foo1, foo2}; | ^^^^ Could not find `bar` in `std` ``` | ||||
| 2016-10-27 | Add semicolon to "Maybe a missing `extern crate foo`" message | Robin Stocker | -1/+1 | |
| I had it a couple of times that I was missing the "extern crate" line after I introduced a new dependency. So I copied the text from the message and inserted it into the beginning of my code, only to find the compiler complaining that I was missing the semicolon. (I forgot to add it after the text that I had pasted.) There's a similar message which does include the semicolon, namely "help: you can import it into scope: `use foo::Bar;`". I think the two messages should be consistent, so this change adds it for "extern crate". | ||||
| 2016-08-22 | Updated E0432 to new format | Knight | -1/+2 | |
| 2015-01-05 | Remove use of globs feature gate from tests. | Huon Wilson | -2/+0 | |
| 2014-06-18 | rustc: reduce redundant resolve errors. | Kevin Butler | -4/+2 | |
| 2014-06-17 | rustc: Add self/super hint for extern crate resolve errors. | Kevin Butler | -2/+2 | |
| 2014-03-28 | Convert most code to new inner attribute syntax. | Brian Anderson | -1/+1 | |
| Closes #2569 | ||||
| 2013-10-06 | Add appropriate #[feature] directives to tests | Alex Crichton | -0/+2 | |
| 2013-05-09 | fix formating and tests | Corey Richardson | -1/+1 | |
| 2013-03-02 | librustc: Forbid chained imports and fix the logic for one-level renaming ↵ | Patrick Walton | -1/+2 | |
| imports | ||||
| 2012-12-28 | test: Fix a bunch of compile-fail tests. rs=bustage | Patrick Walton | -2/+1 | |
| 2012-12-10 | Reliciense makefiles and testsuite. Yup. | Graydon Hoare | -0/+10 | |
| 2012-11-15 | Update error messages and un-xfail | Tim Chevalier | -3/+2 | |
| 2012-09-05 | test: "import" -> "use" | Patrick Walton | -1/+1 | |
| 2012-07-09 | rustc: Switch to the new resolution pass | Patrick Walton | -1/+2 | |
| 2012-07-06 | Revert "rustc: Switch to the new resolution pass" | Niko Matsakis | -2/+1 | |
| This reverts commit c4af6e92fbae171c56a4e68666025725555fc9d8. Branch was burning...many, many unresolved imports. | ||||
| 2012-07-06 | rustc: Switch to the new resolution pass | Patrick Walton | -1/+2 | |
| 2012-06-30 | change the test suite `//! kind` syntax to `//~ kind` in order to avoid a | Gareth Daniel Smith | -2/+2 | |
| conflict with the new single-line-sugared-inner-doc-comment (`//! ...`). | ||||
| 2012-02-22 | test: Add a test for #1697 | Brian Anderson | -0/+7 | |
