Félix Saparelli
Félix Saparelli
The first two (the work done in #88), have been released in 3.0.0.
Nope: https://github.com/notify-rs/notify/blob/main/src/poll.rs#L59-L60
Absolutely! Watchman support has been on the `next` wishlist for a long time, possibly as a "blessed" or "official but external" backend.
Been thinking about this because it provides such a good story both for direct users of the library and for end-users of downstream applications. So, specifically, _to be in core_,...
Hmm, you raise a good point. With the new `Watcher::configure` I could see that we could make "precise events" **opt-in**. In most cases you'd get a `kind: EventKind::Any` that you...
To keep track, this has several components: - [x] Convert debounced mode events to the new struct - [x] Handle errors somehow - [ ] Convert immediate ("raw") mode events...
The new event is a superset of the old so that's actually impossible to do. What you'd do is drill down to exactly as far as you care about, and...
IFF that amount of precision is available from the platform, yes. I've written up The Event Guide which may have more / a comprehensive overview. https://github.com/passcod/notify/wiki/The-Event-Guide On Tue, 23 Apr...
[As an update](https://what.passcod.name/#notify-5-0), I'm currently deep into `debounce/mod.rs`. Everything still looking good, it's just a lot more time-consuming than I originally thought.
You can use the short method with no types: ```rust let mut watcher = immediate_watcher(...)?; ``` The full form (needs a type hint because `Watcher` is a trait): ```rust let...