diff options
| author | Jason Newcomb <jsnewcomb@pm.me> | 2025-06-03 14:03:51 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-03 14:03:51 +0000 |
| commit | eafef8473605f2f9fc5689ef4ba70fc590930d52 (patch) | |
| tree | bf18a2562e0ef4cb75520cceaabdf50da3fc7da3 /compiler/rustc_codegen_llvm/src | |
| parent | 716eadf674f84ba932a0d3b27c18cd07e9839925 (diff) | |
| parent | 43b7d87be1da241ba25d04b1c53508d88fb2eb25 (diff) | |
| download | rust-eafef8473605f2f9fc5689ef4ba70fc590930d52.tar.gz rust-eafef8473605f2f9fc5689ef4ba70fc590930d52.zip | |
`missing_const_for_fn`: consider constness of instance (#14759)
When determining when a function or method can be called from a `const` context, the determination must be made on the instance, not on the declaration. This makes a difference, for example, with `const_trait` traits whose implementations may or may not be `const`. changelog: [`missing_const_for_fn`]: when checking if a function or method can be called from a `const` context, look at the concrete implementation rather than at the trait definition Fixes rust-lang/rust-clippy#14658 r? @Jarcho
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
