| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-02-28 | Merge commit '9f9a822509e5ad3e560cbbe830d1013f936fca28' into ↵ | Philipp Krones | -1/+5 | |
| clippy-subtree-update | ||||
| 2024-02-27 | Merge commit '10136170fe9ed01e46aeb4f4479175b79eb0e3c7' into ↵ | Philipp Krones | -2/+2 | |
| clippy-subtree-update | ||||
| 2023-09-04 | Adjust clippy tests with new rustc help suggestion for lints | Urgau | -0/+2 | |
| 2023-08-24 | Merge commit '080b587854a73f2a8cbaecff1884860a78e2ff37' into clippyup | Philipp Krones | -0/+23 | |
| 2023-07-02 | Merge commit '37f4c1725d3fd7e9c3ffd8783246bc5589debc53' into clippyup | Philipp Krones | -2/+10 | |
| 2021-11-08 | Don't abort compilation after giving a lint error | Joshua Nelson | -1/+2 | |
| 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-12-06 | Merge commit 'c1664c50b27a51f7a78c93ba65558e7c33eabee6' into clippyup | flip1995 | -0/+33 | |
