| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-02-18 | Move methods from `Map` to `TyCtxt`, part 2. | Nicholas Nethercote | -1/+1 | |
| Continuing the work started in #136466. Every method gains a `hir_` prefix, though for the ones that already have a `par_` or `try_par_` prefix I added the `hir_` after that. | ||||
| 2025-02-02 | Convert two `rustc_middle::lint` functions to `Span` methods. | Nicholas Nethercote | -2/+1 | |
| `rustc_middle` is a huge crate and it's always good to move stuff out of it. There are lots of similar methods already on `Span`, so these two functions, `in_external_macro` and `is_from_async_await`, fit right in. The diff is big because `in_external_macro` is used a lot by clippy lints. | ||||
| 2024-12-26 | Merge commit '609cd310be44677ae31d452a17b0f8207e1abfe1' into ↵ | Philipp Krones | -4/+2 | |
| clippy-subtree-update | ||||
| 2024-12-11 | Require the `constness` query to only be invoked on things that can have ↵ | Oli Scherer | -1/+42 | |
| constness | ||||
| 2024-11-28 | Merge commit 'ff4a26d442bead94a4c96fb1de967374bc4fbd8e' into ↵ | Philipp Krones | -2/+2 | |
| clippy-subtree-update | ||||
| 2024-10-18 | Merge commit 'a109190d7060236e655fc75533373fa274ec5343' into ↵ | Philipp Krones | -3/+19 | |
| clippy-subtree-update | ||||
| 2024-08-24 | Merge commit '0f8eabd6231366bfc1bb1464601297c2d48f8f68' into clippyup | Jason Newcomb | -2/+2 | |
| 2024-08-08 | Merge commit 'cb806113e0f83a8f9b47d35b453b676543bcc40e' into ↵ | Philipp Krones | -3/+4 | |
| clippy-subtree-update | ||||
| 2024-07-11 | Merge commit 'b794b8e08c16517a941dc598bb1483e8e12a8592' into ↵ | Philipp Krones | -16/+13 | |
| clippy-subtree-update | ||||
| 2024-06-19 | Resolve Clippy `f16` and `f128` `unimplemented!`/`FIXME`s | Trevor Gross | -0/+2 | |
| This removes the ICE codepaths for `f16` and `f128` in Clippy. `rustc_apfloat` is used as a dependency for the parsing of these types, since their `FromStr` implementation will not be available in the standard library for a while. | ||||
| 2023-12-16 | Merge commit 'a859e5cc1ce100df22346a1005da30532d04de59' into clippyup | Philipp Krones | -1/+3 | |
| 2023-12-01 | Merge commit 'f0cdee4a3f094416189261481eae374b76792af1' into clippy-subtree-sync | Philipp Krones | -1/+1 | |
| 2023-11-02 | Merge commit '09ac14c901abc43bd0d617ae4a44e8a4fed98d9c' into clippyup | Philipp Krones | -44/+38 | |
| 2023-10-07 | Auto merge of #116437 - nnethercote:rustc_features, r=Nilstrieb | bors | -1/+1 | |
| Clean up `rustc_features` Plenty more to be done, but this is a decent start. r? `@Nilstrieb` | ||||
| 2023-10-06 | Merge commit 'b105fb4c39bc1a010807a6c076193cef8d93c109' into clippyup | Philipp Krones | -2/+2 | |
| 2023-10-05 | Rename `Features::active_features`. | Nicholas Nethercote | -1/+1 | |
| The word "active" is currently used in two different and confusing ways: - `ACTIVE_FEATURES` actually means "available unstable features" - `Features::active_features` actually means "features declared in the crate's code", which can include feature within `ACTIVE_FEATURES` but also others. (This is also distinct from "enabled" features which includes declared features but also some edition-specific features automatically enabled depending on the edition in use.) This commit changes the `Features::active_features` to `Features::declared_features` which actually matches its meaning. Likewise, `Features::active` becomes `Features::declared`. | ||||
| 2023-08-11 | Merge commit '1e8fdf492808a25d78a97e1242b835ace9924e4d' into clippyup | Philipp Krones | -1/+1 | |
| 2023-07-27 | bless clippy | Deadbeef | -3/+5 | |
| 2023-07-27 | Remove `constness` from `ParamEnv` | Deadbeef | -1/+1 | |
| 2023-07-17 | Merge commit 'd9c24d1b1ee61f276e550b967409c9f155eac4e3' into clippyup | Philipp Krones | -0/+173 | |
