5 unstable releases

0.3.2 Jul 17, 2023
0.3.1 Feb 25, 2023
0.3.0 Dec 9, 2022
0.2.0 Dec 7, 2022
0.1.0 Dec 6, 2022

#340 in Filesystem

Download history 18/week @ 2024-02-07 30/week @ 2024-02-14 41/week @ 2024-02-21 85/week @ 2024-02-28 56/week @ 2024-03-06 49/week @ 2024-03-13 43/week @ 2024-03-20 38/week @ 2024-03-27 45/week @ 2024-04-03 37/week @ 2024-04-10 29/week @ 2024-04-17 36/week @ 2024-04-24 62/week @ 2024-05-01 93/week @ 2024-05-08 40/week @ 2024-05-15 69/week @ 2024-05-22

271 downloads per month
Used in 2 crates


463 lines


More ways to rename files.


The Rust standard library offers std::fs::rename for renaming files. Sometimes, that's not enough. Consider the example of renaming a file but aborting the operation if something already exists at the destination path. That can be achieved using the Rust standard library but ensuring that the operation is atomic requires platform-specific APIs. Without using platform-specific APIs, a TOCTTOU bug can be introduced. This library aims to provide a cross-platform interface to these APIs.


Renaming a file without the possibility of accidentally overwriting anything can be done using rename_exclusive. It should be noted that this feature is not supported by all combinations of operating system and file system. rename_exclusive will fail if it can't be done atomically.

use std::io::Result;

fn main() -> Result<()> {
    renamore::rename_exclusive("old.txt", "new.txt")

Alternatively, rename_exclusive_fallback can be used. This will try to perform the operation atomically, and use a non-atomic fallback if that's not supported. The return value will indicate what happened.

use std::io::Result;

fn main() -> Result<()> {
    if renamore::rename_exclusive_fallback("old.txt", "new.txt")? {
        // `new.txt` was definitely not overwritten.
        println!("The operation was atomic");
    } else {
        // `new.txt` was probably not overwritten.
        println!("The operation was not atomic");


Platform-specific behaviour

On Linux, the renameat2 syscall is used. A wrapper around this syscall is provided by glibc since version 2.28 but not musl (yet?). The existence of the wrapper is checked at build time and a wrapper is provided if one isn't found. In case something goes wrong, there are two features that can be used to bypass this mechanism.

  • always-supported. Assume that renameat2 exists.
  • always-fallback. Assume that renameat2 doesn't exist.

Hopefully using these features shouldn't be necessary. If they do become necessary, then there might be a bug.


Licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

No runtime deps

~14K SLoC