The readme offers Watcher's design goals, sure, but it doesn't offer the non-goals.
We should add a section on the things that Watcher is not interested in solving (at least at the moment). These are the OS-level caveats to certain system APIs. For inotify, that's events potentially disappearing or being duplicated. For std::filesystem, there are some places where UB might happen, although I haven't looked into exactly when they occur.
These are important caveats that deserve a place in the readme but require more research.
The readme offers Watcher's design goals, sure, but it doesn't offer the non-goals.
We should add a section on the things that Watcher is not interested in solving (at least at the moment). These are the OS-level caveats to certain system APIs. For
inotify
, that's events potentially disappearing or being duplicated. Forstd::filesystem
, there are some places where UB might happen, although I haven't looked into exactly when they occur.These are important caveats that deserve a place in the readme but require more research.