about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
diff options
context:
space:
mode:
authorAaron Hill <aa1ronham@gmail.com>2021-03-14 16:55:59 -0400
committerAaron Hill <aa1ronham@gmail.com>2021-03-14 21:31:46 -0400
commitf190bc4f4736ae0aed9580a2b4ed16bc2d678d11 (patch)
tree14456a9d09d0d9506cc11d24b8f6191a9af9acc8 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
parentd6eaea1c8860adb5302d2fbaad409e36585ab217 (diff)
downloadrust-f190bc4f4736ae0aed9580a2b4ed16bc2d678d11.tar.gz
rust-f190bc4f4736ae0aed9580a2b4ed16bc2d678d11.zip
Introduce `proc_macro_back_compat` lint, and emit for `time-macros-impl`
Now that future-incompat-report support has landed in nightly Cargo, we
can start to make progress towards removing the various proc-macro
back-compat hacks that have accumulated in the compiler.

This PR introduces a new lint `proc_macro_back_compat`, which results in
a future-incompat-report entry being generated. All proc-macro
back-compat warnings will be grouped under this lint. Note that this
lint will never actually become a hard error - instead, we will remove
the special cases for various macros, which will cause older versions of
those crates to emit some other error.

I've added code to fire this lint for the `time-macros-impl` case. This
is the easiest case out of all of our current back-compat hacks - the
crate was renamed to `time-macros`, so seeing a filename with
`time-macros-impl` guarantees that an older version of the parent `time`
crate is in use.

When Cargo's future-incompat-report feature gets stabilized, affected
users will start to see future-incompat warnings when they build their
crates.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions