diff options
| author | Aaron Hill <aa1ronham@gmail.com> | 2021-12-21 16:31:35 -0500 |
|---|---|---|
| committer | Aaron Hill <aa1ronham@gmail.com> | 2021-12-21 16:34:12 -0500 |
| commit | f1d682334d07e125595bb73735b6045bedfb30c4 (patch) | |
| tree | 75b6c4b5469f4166668ab3c67721ee0a169240b0 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | e100ec5bc7cd768ec17d75448b29c9ab4a39272b (diff) | |
| download | rust-f1d682334d07e125595bb73735b6045bedfb30c4.tar.gz rust-f1d682334d07e125595bb73735b6045bedfb30c4.zip | |
Add `#[rustc_clean(loaded_from_disk)]` to assert loading of query result
Currently, you can use `#[rustc_clean]` to assert to that a particular query (technically, a `DepNode`) is green or red. However, a green `DepNode` does not mean that the query result was actually deserialized from disk - we might have never re-run a query that needed the result. Some incremental tests are written as regression tests for ICEs that occured during query result decoding. Using `#[rustc_clean(loaded_from_disk="typeck")]`, you can now assert that the result of a particular query (e.g. `typeck`) was actually loaded from disk, in addition to being green.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
