diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-09-05 19:43:46 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-05 19:43:46 +0200 |
| commit | 46f390f047309c943a7b773ae1f4c225a8d65907 (patch) | |
| tree | ec86d99ba6779d65399885e6a9d42e92a75fc5c4 /compiler/rustc_codegen_llvm/src | |
| parent | eb33b43bab08223fa6b46abacc1e95e859fe375d (diff) | |
| parent | 040239465aefc09f8c837ff9d4d66ca6297e5c5c (diff) | |
| download | rust-46f390f047309c943a7b773ae1f4c225a8d65907.tar.gz rust-46f390f047309c943a7b773ae1f4c225a8d65907.zip | |
Rollup merge of #128919 - Nadrieril:lint-query-leaks, r=cjgillot
Add an internal lint that warns when accessing untracked data Some methods access data that is not tracked by the query system and should be used with caution. As suggested in https://github.com/rust-lang/rust/pull/128815#issuecomment-2275488683, in this PR I propose a lint (modeled on the `potential_query_instability` lint) that warns when using some specially-annotatted functions. I can't tell myself if this lint would be that useful, compared to renaming `Steal::is_stolen` to `is_stolen_untracked`. This would depend on whether there are other functions we'd want to lint like this. So far it seems they're called `*_untracked`, which may be clear enough. r? ``@oli-obk``
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions