| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 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 | |
