Update or write rust bindings for libuv

[creationix]

No description provided.

[Qard]

I updated libuv-sys to support 1.9.1 just the other day. You could ask @sorear to push it up to crates.io. It still lacks a higher-level, Rust-friendly abstract API though.

[creationix]

@Qard, thanks, that sounds useful.

I did have a question that you might know the answer. I'm considering a pure rust version of nucleus using rjs and the rust stblib instead of binding to libuv. Are there parts in the libuv API that would hard to simulate using rusts standard libraries and pure rust libs on crates.io?

[sorear]

@creationix Rust has no multiplexed I/O facility in the standard library whatsoever. If you're doing Rust and avoiding FFI for whatever reason, you need one thread per open socket. This is why I started the UV binding in the first place, although the database server I was planning to write has languished for other reasons, so I never got around to writing the high-level UV interface. I think I was going to do a callback-based interface but handling ownership with Rc stuff, but it's a bit fuzzy. Also, microtasks (I found a way to do the moral equivalent of a Deque<Box<FnOnce()>> with no memory allocation, for a neat trick).

There are other Rust libraries (necessarily using FFI because the above) for doing multiplexed I/O, but at the time I scoped out the project they looked various combinations of immature and overengineered. Better to wrap something time-tested.

[creationix]

@sorear thanks, that's helpful information.