BurntSushi / BurntSushi/same-file
Question about methodology
Open
enhancement
- Dominant language
- Rust
- Stars
- 124
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Sorry to be opening an issue for a question. I was curious why this library exists compared to `std::fs::canonicalize`, which has the guarantee of Rust to return the real path. Is it a race condition commentary where
- open file
- move file
- move other file to that location
would cause distinct files to return as matches due to having the same path across time, an edge case this lib handles? What stronger guarantees *exactly* does this library aim to offer?
This may benefit from a follow-up to the README clarifying its utility.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.