There are lots of other event loops out there. Libevent is optimized for high-performance network IO in environments with many, many sockets. But there are also tons of loops for other things, like GUI libraries and so on.
We should find loops that are currently hard to integrate well with libevent, and see what hooks we can add to the code to make them work better.
Marc Lehmann said (of libev):
* I added idle watchers, pid watchers and hook watchers into the event loop,
as is required for integration of other event-based libraries, without
having to force the use of some construct around event_loop.
We should figure out which loops these are, so we can figure out what kind of new features are suitable.
This thread some has ideas of how we would do this:
http://archives.seul.org/libevent/users/Dec-2009/msg00000.html