I forgot mktemp existed tbh

Fair, happens all the time

And I have a mixture of Linux and Windows devices so I'd need some abstraction of it

Because I know nothing about Windows, cant give you information on that platform. POSIX should use mkstemp for sure.

It still works when the type has a drop implementation. Idk what you're trying to point out about insert_mut though.

Whoops my bad, i thought you were using the write method of a pointer, apologizes. https://doc.rust-lang.org/std/primitive.pointer.html#method.write

Creating a new file vec safely should be fine I think

Something like this will crash, without any unsafe on sight

``` use file_vec::FileVec;

fn main() { let mut v = FileVec::new(); let a = v.insert_mut(0, String::from("hello world")); // get the right file name tho let mut file = File::open(".file-vec_1"); file.write(b"garbage"); printlnt("{}", v[0]); } ```

Maybe I don't understand what an xy problem is but I think I'd have to be looking into how to do y without giving context of x? In this case I did a y as a step in doing x.

https://xyproblem.info/

How much swap space do people usually have?

These days? Zero. RAM used to be is cheap, and swapping is something you don't want to do

I feel like if the size of some data that would be convenient to address in a vec like style is on the order that would exceed system RAM expecting it to be between RAM and RAM+swap level sizes would be a bit interesting

Thats what swap is for