collect watchpoints when underlying watch was removed outside notify about notify

[rjeczalik]

The issue is two-fold - it won't work perfectly across platforms as Windows does not notify about removed watches:

Retrieves information that describes the changes within the specified directory. The function does not report changes to the specified directory itself.

The most proper way to deal with this is to set a watchpoint on a path which is guaranteed to not be gone, when we do care to receive events for whole lifetime of our application (those paths being equivalent to %userprofile%, $GOPATH, $TMPDIR etc.).

If for some reason we still need to maintain watcher lifetime to ensure underlying watch is not stopped outside notify, the solution is to listen on Delete event, call Stop on the listening channel and call Watch the path again when we know it's back (most likely by watching a priori its parent for Create). However it's so cumbersome to implement, both by the user or by notify itself, that I doubt anyone will need it. Moreover it would create unnecessary overhead, as every path would need to be implicitly watched for Delete event as well.

[mauricioabreu]

I guess this is exactly the problem I am having on #171 It looks like the solution here is the one you mentioned.