diff options
| author | bors <bors@rust-lang.org> | 2024-06-11 15:50:25 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-06-11 15:50:25 +0000 |
| commit | 3ea5e236ecb4c5f22437059f82d3915d311e4ec0 (patch) | |
| tree | d53e401384bc689dfab71897283ef6c03638e8a1 /compiler/rustc_query_impl/src/lib.rs | |
| parent | 0c960618b56f662d933e8b864cd9632a99174e87 (diff) | |
| parent | c84afee89851f0d0d5089d64d35225a6adb28453 (diff) | |
| download | rust-3ea5e236ecb4c5f22437059f82d3915d311e4ec0.tar.gz rust-3ea5e236ecb4c5f22437059f82d3915d311e4ec0.zip | |
Auto merge of #125736 - Oneirical:run-make-file-management, r=jieyouxu
run-make-support: add wrapper for `fs` operations Suggested by #125728. The point of this wrapper is to stop silent fails caused by forgetting to `unwrap` `fs` functions. However, functions like `fs::read` which return something and get stored in a variable should cause a failure on their own if they are not unwrapped (as the `Result` will be stored in the variable, and something will be done on that `Result` that should have been done to its contents). Is it still pertinent to wrap `fs::read_to_string`, `fs::metadata` and so on? Closes: https://github.com/rust-lang/rust/issues/125728 try-job: x86_64-msvc try-job: i686-mingw
Diffstat (limited to 'compiler/rustc_query_impl/src/lib.rs')
0 files changed, 0 insertions, 0 deletions