Proposal: split Event structure into its own crate (notify-events?)

[passcod]

This is a proposal to only split out the notify/src/event.rs file into its own crate, which would have no required dependencies, and serde only when the feature is enabled.

The Event struct and child enums are pretty infrequently changed, and it would be helpful to downstream crates/users to be able to use the notify event types without pulling the entire notify runtime.

My specific motivation is for a usage across an IPC or network barrier, where one side does the file watching and the other wants to deserialize into the proper types.

[0xpr03]

I don't see a problem with doing that. Some people will probably defend against a multi-crate setup, but if that helps, why not.

Only incoming breaking change would be one proposal for making #478 possible.

[0xpr03]

Only bikeshed is the crate name. notify-events is fine-ish ? notify-types is probably more fitting

[dfaust]

Oops, I just noticed that the debouncer crates have their own DebouncedEvent types.

What should we do about those?

1. Create notify-debouncer-mini-types and notify-debouncer-full-types crates
2. Move them into the notify-types crate
3. Do nothing

[0xpr03]

Option 2 should be fine. Not perfect but also it doesn't hurt anyone.