You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is where I'm going to keep a list of known pain points with tempfile v3 that can't be fixed without breaking changes. I don't know if we'll ever have a v4, but if we do, we can revisit everything on this list:
The builder has two lifetime parameters making it awkward to add additional fields with new lifetime parameters. Ideally, it would just have a single lifetime and we'd rely on subtyping.
Take shared advisory locks on all named temporary files to prevent temporary file cleaners from deleting them. This could break some things so we have to be careful, but taking a shared lock is probably reasonable? Possibly only do this if the parent directory is +t (sticky)?
The text was updated successfully, but these errors were encountered:
I'd expect the #59 fix to require a major version update, it's not obvious to users whether that's a bug or intended behavior, so that should be assumed as breaking IMHO.
EDIT: that is, if the fix is to make that function panic.
This is where I'm going to keep a list of known pain points with tempfile v3 that can't be fixed without breaking changes. I don't know if we'll ever have a v4, but if we do, we can revisit everything on this list:
TempDir
implementsAsRef<Path>
making it easy to accidentally drop it.+t
(sticky)?The text was updated successfully, but these errors were encountered: