diff options
| author | Michael Baikov <manpacket@gmail.com> | 2024-06-13 08:27:21 -0400 |
|---|---|---|
| committer | Michael Baikov <manpacket@gmail.com> | 2024-06-19 07:21:41 -0400 |
| commit | db5ed4bd799cda1217ec6431ffa56cecd09ef6e9 (patch) | |
| tree | 3d95e8d876a4389bfcb9e8ae07a95ca1be53dffa /compiler/rustc_interface/src/errors.rs | |
| parent | 3c0f019b3c56c1a0e6e0cbed6f8a8b0b245e5665 (diff) | |
| download | rust-db5ed4bd799cda1217ec6431ffa56cecd09ef6e9.tar.gz rust-db5ed4bd799cda1217ec6431ffa56cecd09ef6e9.zip | |
Allow for try_force_from_dep_node to fail
The way it is implemented currently try_force_from_dep_node returns true as long as there's a function to force the query. It wasn't this way from the beginning, earlier version was producing forcing result and it was changed in https://github.com/rust-lang/rust/pull/89978, I couldn't find any comments addressing this change. One way it can fail is by failing to recover the query in DepNodeParams::recover - when we are trying to query something that no longer exists in the current environment
Diffstat (limited to 'compiler/rustc_interface/src/errors.rs')
0 files changed, 0 insertions, 0 deletions