about summary refs log tree commit diff
path: root/tests/rustdoc/source-code-pages
diff options
context:
space:
mode:
authorSamuel Tardieu <sam@rfc1149.net>2025-02-13 13:46:30 +0100
committerSamuel Tardieu <sam@rfc1149.net>2025-02-28 23:15:29 +0100
commit4f0e507165ae6ebf3304041324c196a6e5ae801c (patch)
tree6de6ccd682d26eb3f26954573c4ae6baa1d32b71 /tests/rustdoc/source-code-pages
parent9f9a822509e5ad3e560cbbe830d1013f936fca28 (diff)
downloadrust-4f0e507165ae6ebf3304041324c196a6e5ae801c.tar.gz
rust-4f0e507165ae6ebf3304041324c196a6e5ae801c.zip
`incompatible_msrv`: lint function calls with any argument count
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.
Diffstat (limited to 'tests/rustdoc/source-code-pages')
0 files changed, 0 insertions, 0 deletions