about summary refs log tree commit diff
path: root/library/std/src/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorDylan DPC <dylan.dpc@gmail.com>2021-03-15 16:22:57 +0100
committerGitHub <noreply@github.com>2021-03-15 16:22:57 +0100
commitd1f5f1d156dc68b4ca13678f3a63515df0b2e348 (patch)
treeae2608e6e324872eb7949e9da1c42baf5d88432f /library/std/src/sys/unix/stack_overflow.rs
parent8ec9b2a0acc5cde19236d777cb197d19f863bd8a (diff)
parentf190bc4f4736ae0aed9580a2b4ed16bc2d678d11 (diff)
downloadrust-d1f5f1d156dc68b4ca13678f3a63515df0b2e348.tar.gz
rust-d1f5f1d156dc68b4ca13678f3a63515df0b2e348.zip
Rollup merge of #83127 - Aaron1011:time-macros-impl-warn, r=petrochenkov
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 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions