| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -11/+0 | |
| 2020-03-21 | Bless tests | LeSeulArtichaut | -6/+4 | |
| 2019-10-27 | Point at local similarly named element and tweak references to variants | Esteban Küber | -2/+7 | |
| Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method. | ||||
| 2019-09-15 | resolve: Remove `!` from "cannot find" diagnostics for macros | Vadim Petrochenkov | -1/+1 | |
| 2019-07-18 | resolve: Visit all scopes to collect suggestion candidates for unresolved macros | Vadim Petrochenkov | -1/+1 | |
| 2019-03-11 | Update tests | Vadim Petrochenkov | -1/+1 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -1/+1 | |
| 2018-08-17 | Stabilize `use_extern_macros` | Vadim Petrochenkov | -9/+1 | |
| 2018-02-26 | Update UI tests | Vadim Petrochenkov | -2/+2 | |
| 2018-01-15 | Don't include bang in macro replacement suggestion | Ryan Cumming | -1/+1 | |
| When we suggest the replacement for a macro we include the "!" in the suggested replacement but the span only contains the name of the macro itself. Using that replacement would cause a duplicate "!" in the resulting code. I originally tried to extend the span to be replaced by 1 byte in rust-lang/rust#47424. However, @zackmdavis pointed out that there can be whitespace between the macro name and the bang. Instead, just remove the bang from the suggested replacement. Fixes #47418 | ||||
| 2017-11-24 | Merge cfail and ui tests into ui tests | Oliver Schneider | -2/+2 | |
| 2017-07-17 | Change some helps to suggestions | Oliver Schneider | -4/+2 | |
| 2017-07-17 | Move some tests from compile-fail to ui | Oliver Schneider | -0/+18 | |
