about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
diff options
context:
space:
mode:
authorCatherine Flores <catherine.3.flores@gmail.com>2025-03-13 04:11:42 +0000
committerGitHub <noreply@github.com>2025-03-13 04:11:42 +0000
commit18061e2c42c719d0d483b9bebdc853ec189ba121 (patch)
tree04f2fc59830586cd4ee0762b1a79332ba4363291 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
parent72540726b145ebeee28383e94d9c2e4f713d3a18 (diff)
parent4f0e507165ae6ebf3304041324c196a6e5ae801c (diff)
downloadrust-18061e2c42c719d0d483b9bebdc853ec189ba121.tar.gz
rust-18061e2c42c719d0d483b9bebdc853ec189ba121.zip
`incompatible_msrv`: lint function calls with any argument count (#14216)
The lint for function calls was previously restricted to functions
taking exactly one argument. This was not documented.

Generalizing the lint to an arbitrary number of arguments in the
function call requires special casing some macro expansions from the
standard library. Macros such as `panic!()` or `assert_eq!()` exist
since Rust 1.0.0, but modern stdlib expand those macros into calls to
functions introduced in later Rust versions. While it is desirable to
lint code inside macros, using MSRV-incompatible functions coming from
`core` in macro expansions has been special-cased to not trigger this
lint.

Also, code coming from compiler desugaring may contain function calls
(for example, `a..=b` is now desugared into `RangeInclusive::new(a, b)`.
Those should not be linted either as the compiler is allowed to use
unstable function calls.

Fix #14212

changelog: [`incompatible_msrv`]: lint function calls with any argument
count
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions