| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -24/+0 | |
| 2021-11-08 | Don't abort compilation after giving a lint error | Joshua Nelson | -1/+9 | |
| The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors. | ||||
| 2020-01-24 | Normalise notes with the/is | varkor | -1/+1 | |
| 2019-09-21 | Do not trigger unreachable lint in async body and Use span labels | Esteban Küber | -6/+3 | |
| 2019-09-18 | Point at original span when emitting unreachable lint | Aaron Hill | -0/+5 | |
| Fixes #64590 When we emit an 'unreachable' lint, we now add a note pointing at the expression that actually causes the code to be unreachable (e.g. `return`, `break`, `panic`). This is especially useful when macros are involved, since a diverging expression might be hidden inside of a macro invocation. | ||||
| 2019-03-11 | Update tests | Vadim Petrochenkov | -1/+1 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -2/+2 | |
| 2018-08-14 | Merged migrated compile-fail tests and ui tests. Fixes #46841. | David Wood | -0/+14 | |
