remove_dir_all

Reliable parallel remove_dir_all implementation for Windows and other platforms.

Latest version: 1.0.0 registry icon
Maintenance score
49
Safety score
99
Popularity score
75
Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.
Security
  Vulnerabilities
Version Suggest Low Medium High Critical
1.0.0 0 0 0 0 0
0.8.4 0 0 0 0 0
0.8.3 0 0 0 0 0
0.8.2 0 0 0 0 0
0.8.1 0 0 0 0 0
0.8.0 0 0 0 0 0
0.7.0 0 0 1 0 0
0.6.1 0 0 1 0 0
0.6.0 0 0 1 0 0
0.5.3 0 0 1 0 0
0.5.2 0 0 1 0 0
0.5.1 0 0 1 0 0
0.5.0 0 0 1 0 0
0.3.0 0 0 1 0 0
0.2.0 0 0 1 0 0
0.1.0 0 0 1 0 0

Stability
Latest release:

1.0.0 - This version may not be safe as it has not been updated for a long time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

MIT   -   MIT License

Not a wildcard

Not proprietary

OSI Compliant


Apache-2.0   -   Apache License 2.0

Not a wildcard

Not proprietary

OSI Compliant



remove_dir_all

Latest Version Docs License

Description

Reliable and fast directory removal functions.

  • remove_dir_all - on non-Windows this is a re-export of std::fs::remove_dir_all. For Windows an implementation that handles the locking of directories that occurs when deleting directory trees rapidly.

  • remove_dir_contents - as for remove_dir_all but does not delete the supplied root directory.

  • ensure_empty_dir - as for remove_dir_contents but will create the directory if it does not exist.

extern crate remove_dir_all;

use remove_dir_all::*;

fn main() {
    remove_dir_all("./temp/").unwrap();
    remove_dir_contents("./cache/").unwrap();
}

Minimum Rust Version

The minimum rust version for remove_dir_all is the latest stable release, and the minimum version may be bumped through patch releases. You can pin to a specific version by setting by add = to your version (e.g. =0.6.0), or commiting a Cargo.lock file to your project.