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
Hi! I have a use case1 where both the atime and mtime are optional and where following the symlink is optional. While looking through the source code of this crate, I found this function in the unix-specific part of the library, which fits my use case perfectly, but it's not public:
Similar functions do not yet exist for the Windows and Redox implementations, but I think those could be added with relatively little effort.
If you decide to expose this, I'd recommend a name like set_path_times, mirroring the set_file_handle_times name, which is very similar in functionality. I would be happy to open a PR for this.
This would also partially fix #83, albeit not in the most elegant way.
Footnotes
The touch utility of uutils, which basically acts as a wrapper around the utimensat syscall and therefore requires the same flexibility. ↩
The text was updated successfully, but these errors were encountered:
Hi! I have a use case1 where both the atime and mtime are optional and where following the symlink is optional. While looking through the source code of this crate, I found this function in the unix-specific part of the library, which fits my use case perfectly, but it's not public:
filetime/src/unix/linux.rs
Lines 87 to 92 in 5eec5a5
Similar functions do not yet exist for the Windows and Redox implementations, but I think those could be added with relatively little effort.
If you decide to expose this, I'd recommend a name like
set_path_times
, mirroring theset_file_handle_times
name, which is very similar in functionality. I would be happy to open a PR for this.This would also partially fix #83, albeit not in the most elegant way.
Footnotes
The
touch
utility ofuutils
, which basically acts as a wrapper around theutimensat
syscall and therefore requires the same flexibility. ↩The text was updated successfully, but these errors were encountered: