forked from rust-lang/rust
-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Auto merge of rust-lang#125736 - Oneirical:run-make-file-management, …
…r=jieyouxu run-make-support: add wrapper for `fs` operations Suggested by rust-lang#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: rust-lang#125728 try-job: x86_64-msvc try-job: i686-mingw
- Loading branch information
Showing
36 changed files
with
211 additions
and
108 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,113 @@ | ||
use std::fs; | ||
use std::path::Path; | ||
|
||
/// A wrapper around [`std::fs::remove_file`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn remove_file<P: AsRef<Path>>(path: P) { | ||
fs::remove_file(path.as_ref()) | ||
.expect(&format!("the file in path \"{}\" could not be removed", path.as_ref().display())); | ||
} | ||
|
||
/// A wrapper around [`std::fs::copy`] which includes the file path in the panic message. | ||
#[track_caller] | ||
pub fn copy<P: AsRef<Path>, Q: AsRef<Path>>(from: P, to: Q) { | ||
fs::copy(from.as_ref(), to.as_ref()).expect(&format!( | ||
"the file \"{}\" could not be copied over to \"{}\"", | ||
from.as_ref().display(), | ||
to.as_ref().display(), | ||
)); | ||
} | ||
|
||
/// A wrapper around [`std::fs::File::create`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn create_file<P: AsRef<Path>>(path: P) { | ||
fs::File::create(path.as_ref()) | ||
.expect(&format!("the file in path \"{}\" could not be created", path.as_ref().display())); | ||
} | ||
|
||
/// A wrapper around [`std::fs::read`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn read<P: AsRef<Path>>(path: P) -> Vec<u8> { | ||
fs::read(path.as_ref()) | ||
.expect(&format!("the file in path \"{}\" could not be read", path.as_ref().display())) | ||
} | ||
|
||
/// A wrapper around [`std::fs::read_to_string`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn read_to_string<P: AsRef<Path>>(path: P) -> String { | ||
fs::read_to_string(path.as_ref()).expect(&format!( | ||
"the file in path \"{}\" could not be read into a String", | ||
path.as_ref().display() | ||
)) | ||
} | ||
|
||
/// A wrapper around [`std::fs::read_dir`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn read_dir<P: AsRef<Path>>(path: P) -> fs::ReadDir { | ||
fs::read_dir(path.as_ref()) | ||
.expect(&format!("the directory in path \"{}\" could not be read", path.as_ref().display())) | ||
} | ||
|
||
/// A wrapper around [`std::fs::write`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn write<P: AsRef<Path>, C: AsRef<[u8]>>(path: P, contents: C) { | ||
fs::write(path.as_ref(), contents.as_ref()).expect(&format!( | ||
"the file in path \"{}\" could not be written to", | ||
path.as_ref().display() | ||
)); | ||
} | ||
|
||
/// A wrapper around [`std::fs::remove_dir_all`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn remove_dir_all<P: AsRef<Path>>(path: P) { | ||
fs::remove_dir_all(path.as_ref()).expect(&format!( | ||
"the directory in path \"{}\" could not be removed alongside all its contents", | ||
path.as_ref().display(), | ||
)); | ||
} | ||
|
||
/// A wrapper around [`std::fs::create_dir`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn create_dir<P: AsRef<Path>>(path: P) { | ||
fs::create_dir(path.as_ref()).expect(&format!( | ||
"the directory in path \"{}\" could not be created", | ||
path.as_ref().display() | ||
)); | ||
} | ||
|
||
/// A wrapper around [`std::fs::create_dir_all`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn create_dir_all<P: AsRef<Path>>(path: P) { | ||
fs::create_dir_all(path.as_ref()).expect(&format!( | ||
"the directory (and all its parents) in path \"{}\" could not be created", | ||
path.as_ref().display() | ||
)); | ||
} | ||
|
||
/// A wrapper around [`std::fs::metadata`] which includes the file path in the panic message.. | ||
#[track_caller] | ||
pub fn metadata<P: AsRef<Path>>(path: P) -> fs::Metadata { | ||
fs::metadata(path.as_ref()).expect(&format!( | ||
"the file's metadata in path \"{}\" could not be read", | ||
path.as_ref().display() | ||
)) | ||
} | ||
|
||
/// A wrapper around [`std::fs::rename`] which includes the file path in the panic message. | ||
#[track_caller] | ||
pub fn rename<P: AsRef<Path>, Q: AsRef<Path>>(from: P, to: Q) { | ||
fs::rename(from.as_ref(), to.as_ref()).expect(&format!( | ||
"the file \"{}\" could not be moved over to \"{}\"", | ||
from.as_ref().display(), | ||
to.as_ref().display(), | ||
)); | ||
} | ||
|
||
/// A wrapper around [`std::fs::set_permissions`] which includes the file path in the panic message. | ||
#[track_caller] | ||
pub fn set_permissions<P: AsRef<Path>>(path: P, perm: fs::Permissions) { | ||
fs::set_permissions(path.as_ref(), perm).expect(&format!( | ||
"the file's permissions in path \"{}\" could not be changed", | ||
path.as_ref().display() | ||
)); | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.