#across #data #consistent #filenames #different #temporary #generate

temp_file_name

generate temporary filenames and paths from a hash of arbitrary data so that they are consistent across different crates

1 unstable release

0.1.0 Oct 23, 2020

#1480 in Filesystem

Download history 3/week @ 2024-01-07 4/week @ 2024-01-14 1/week @ 2024-01-21 7/week @ 2024-02-11 11/week @ 2024-02-18 24/week @ 2024-02-25 15/week @ 2024-03-03 16/week @ 2024-03-10 16/week @ 2024-03-17 22/week @ 2024-03-24 53/week @ 2024-03-31 10/week @ 2024-04-07 9/week @ 2024-04-14 22/week @ 2024-04-21

95 downloads per month
Used in 6 crates (5 directly)

MIT/Apache

6KB
68 lines

This is a tiny crate with one purpose: generate temporary filenames from a hash of arbitrary data so that they are consistent across different crates. Its intended purpose is to either - give a consistent name, which can -- for example -- be used to cache the expensive output of an input across runs, - or to allow a caller to know what filename a different crate will have given some abstract data. It would be trivially easy to replicate; it exists primarily to allow consistency across otherwise unrelated crates when handling data


lib.rs:

This is a tiny crate with one purpose: generate temporary filenames from a hash of arbitrary data so that they are consistent across different crates. Its intended purpose is to either

  • give a consistent name, which can -- for example -- be used to cache the expensive output of an input across runs,
  • or to allow a caller to know what filename a different crate will have given some abstract data.

It would be trivially easy to replicate; it exists primarily to allow consistency across otherwise unrelated crates when handling data

No runtime deps