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 wrote this crate: https://crates.io/crates/filetime_creation
It extends the functionality of "filetime" to modify the file creation time on Windows.
Initially my idea was to make changes directly on "filetime" and submit a pull request for the changes to be fed back upstream. But take into account the following factors:
This change requires modifying the signature of the existing function, I'm not sure how this will affect SemVer.
Does a feature that only works on Windows affect the cross-platform nature of this crate.
Is it appropriate for other platforms to simply ignore the "ctime" parameter? If inappropriate, do other platforms have suitable means of modifying the file creation time.
Is "ctime" an appropriate name.
So I decided to implement this feature first as a standalone crate to meet my (and potentially others') needs. But in the long run I think this feature should be merged into this crate to avoid community splits.
So what do you think? Should this feature be merged into this crate or should it remain separate? If you can think of a good way to implement this functionality into this crate, I don't mind deprecating my crate and archive the corresponding repository.
The text was updated successfully, but these errors were encountered:
Hi, I wrote this crate: https://crates.io/crates/filetime_creation
It extends the functionality of "filetime" to modify the file creation time on Windows.
Initially my idea was to make changes directly on "filetime" and submit a pull request for the changes to be fed back upstream. But take into account the following factors:
So I decided to implement this feature first as a standalone crate to meet my (and potentially others') needs. But in the long run I think this feature should be merged into this crate to avoid community splits.
So what do you think? Should this feature be merged into this crate or should it remain separate? If you can think of a good way to implement this functionality into this crate, I don't mind deprecating my crate and archive the corresponding repository.
The text was updated successfully, but these errors were encountered: