diff options
| author | bors <bors@rust-lang.org> | 2024-12-23 22:14:38 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-12-23 22:14:38 +0000 |
| commit | 65fe42a5f46a17ac63b21684b7ec8327f1a4c86b (patch) | |
| tree | e7076305aad79821f2eb168248369ec594f2e872 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | bdc6b3de48646345549fd2fe9f62370f56e3fa56 (diff) | |
| parent | b893221517243d942ab503793f885dcefbfa4f45 (diff) | |
| download | rust-65fe42a5f46a17ac63b21684b7ec8327f1a4c86b.tar.gz rust-65fe42a5f46a17ac63b21684b7ec8327f1a4c86b.zip | |
Auto merge of #134493 - compiler-errors:drops-elaborated, r=oli-obk
Always run `tail_expr_drop_order` lint in promoted MIR query Rather than running the lint at the beginning of `mir_drops_elaborated_and_const_checked`, run it at the end of `mir_promoted`. This should ensure that the lint gets picked up when running `cargo fix`, which runs with `--emit metadata` and therefore doesn't actually query `mir_drops_elaborated_and_const_checked`. We could probably push this down into `mir_built` too? but I don't really see a good reason to do so. https://github.com/rust-lang/rust/issues/132861#issuecomment-2539960199 cc `@ehuss`
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions