I'm wondering where os/fsnotify is at and where it needs to be to make the
March 1st code freeze... and with ample time to also use it in cmd/go.
My effort towards this has been fairly sporadic thus far. Sorry about that.
The CL/pull request that I started on GitHub in September is getting fairly
close. It has recursive watching and various filters that many people
(including myself) have implemented on top in the past. There are still
some optimizations we can do to save file handles when filters are
specified, or to take advantage of OS level support for recursive watching
on Windows and OS X (with a future FSEvents adapter).
My CL also has some interfaces to make it easier to write unit tests. Until
now it only had 5 seconds worth of integration tests (which I'm skipping on
the short run).
I'd like to get these changes into the hands of people prior to Go 1.3...
so that it's well tested prior to release. There's also the small matter of
getting all this over to Mercurial (go.exp or os/fsnotify) and the issues
into the Go issue tracker. How do we want to do this, and when?
Finally, Russ Cox mentioned doing an API design doc. Do we have a
template/starting point? Can anyone just start the Google Doc?
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.