diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2021-03-19 15:03:23 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-19 15:03:23 +0100 |
| commit | 75571a5ac0aae9355ace495fb7aac06da963eee9 (patch) | |
| tree | 1c56ef3216b9c3ec5b2d7798b9d1811f22e8029f /compiler/rustc_codegen_llvm/src | |
| parent | db4a97c4cbcb160b3754c803284dd0110d1de1e4 (diff) | |
| parent | 390d1ef6d048563502458ae20d9b7d69d914a680 (diff) | |
| download | rust-75571a5ac0aae9355ace495fb7aac06da963eee9.tar.gz rust-75571a5ac0aae9355ace495fb7aac06da963eee9.zip | |
Rollup merge of #83179 - Aaron1011:actix-web-lint, r=petrochenkov
Extend `proc_macro_back_compat` lint to `actix-web` Unlike the other cases of this lint, there's no simple way to detect if an old version of the relevant crate (`syn`) is in use. The `actix-web` crate only depends on `pin-project` v1.0.0, so checking the version of `actix-web` does not guarantee that a new enough version of `pin-project` (and therefore `syn`) is in use. Instead, we rely on the fact that virtually all of the regressed crates are pinned to a pre-1.0 version of `pin-project`. When this is the case, bumping the `actix-web` dependency will pull in the *latest* version of `pin-project`, which has an explicit dependency on a newer v dependency on a newer version of `syn`. The lint message tells users to update `actix-web`, since that's what they're most likely to have control over. We could potentially tell them to run `cargo update -p syn`, but I think it's more straightforward to suggest an explicit change to the `Cargo.toml` The `actori-web` fork had its last commit over a year ago, and appears to just be a renamed fork of `actix-web`. Therefore, I've removed the `actori-web` check entirely - any crates that actually get broken can simply update `syn` themselves.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
