I'm not sure what the desired semantics for Futures and multiple loops is.  On the one hand, there is little point in having two event loops in the same thread at once (except for testing purposes).  On the other hand, the Future implementation is entirely not thread-safe (btw, the constructor optimistically claims the done callbacks are scheduled using call_soon_threadsafe(), but the implementation actually calls call_soon()).