| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-10-30 | Use match ergonomics compatible with editions 2021 and 2024 | Samuel Tardieu | -1/+1 | |
| 2024-07-17 | Refactor for using config values: | Jason Newcomb | -8/+10 | |
| * Construct lint passes by taking `Conf` by reference. * Use `HashSet` configs in less places * Move some `check_crate` code into the pass constructor when possible. | ||||
| 2024-07-05 | Refactor `disallowed_script_idents`: Simplify script checking loop. | Jason Newcomb | -23/+18 | |
| 2024-05-23 | For restriction lints, replace “Why is this bad?” with “Why restrict ↵ | Kevin Reid | -2/+2 | |
| this?” The `restriction` group contains many lints which are not about necessarily “bad” things, but style choices — perhaps even style choices which contradict conventional Rust style — or are otherwise very situational. This results in silly wording like “Why is this bad? It isn't, but ...”, which I’ve seen confuse a newcomer at least once. To improve this situation, this commit replaces the “Why is this bad?” section heading with “Why restrict this?”, for most, but not all, restriction lints. I left alone the ones whose placement in the restriction group is more incidental. In order to make this make sense, I had to remove the “It isn't, but” texts from the contents of the sections. Sometimes further changes were needed, or there were obvious fixes to make, and I went ahead and made those changes without attempting to split them into another commit, even though many of them are not strictly necessary for the “Why restrict this?” project. | ||||
| 2024-04-01 | fix fallout from previous commit | y21 | -1/+1 | |
| 2024-03-05 | Rename all `ParseSess` variables/fields/lifetimes as `psess`. | Nicholas Nethercote | -1/+1 | |
| Existing names for values of this type are `sess`, `parse_sess`, `parse_session`, and `ps`. `sess` is particularly annoying because that's also used for `Session` values, which are often co-located, and it can be difficult to know which type a value named `sess` refers to. (That annoyance is the main motivation for this change.) `psess` is nice and short, which is good for a name used this much. The commit also renames some `parse_sess_created` values as `psess_created`. | ||||
| 2023-12-01 | Merge commit 'f0cdee4a3f094416189261481eae374b76792af1' into clippy-subtree-sync | Philipp Krones | -1/+1 | |
| 2023-11-02 | Merge commit '09ac14c901abc43bd0d617ae4a44e8a4fed98d9c' into clippyup | Philipp Krones | -1/+1 | |
| 2023-04-11 | Merge commit '83e42a2337dadac915c956d125f1d69132f36425' into clippyup | Philipp Krones | -1/+1 | |
| 2022-10-06 | Merge commit 'ac0e10aa68325235069a842f47499852b2dee79e' into clippyup | Philipp Krones | -2/+1 | |
| 2022-01-23 | Update clippy | Vadim Petrochenkov | -2/+2 | |
| 2021-12-06 | Merge commit 'a5d597637dcb78dc73f93561ce474f23d4177c35' into clippyup | flip1995 | -0/+1 | |
| 2021-07-29 | Merge commit '0cce3f643bfcbb92d5a1bb71858c9cbaff749d6b' into clippyup | flip1995 | -5/+5 | |
| 2021-07-01 | Merge commit '61eb38aeda6cb54b93b872bf503d70084c4d621c' into clippyup | flip1995 | -0/+112 | |
