Benoît Labaere
Benoît Labaere
I really enjoyed the series "Map and Bind and Apply, Oh my!", and each step clicked nicely, until I tried to make sense of this line in "Understanding traverse and...
Nanomsg has latency and throughput [measurement utilities](https://github.com/nanomsg/nanomsg/tree/master/perf). They should be ported to scaproust.
@thehydroimpulse I noticed the appveyor script is using the nightly build of rust while the travis one is using version 1.0.0. How do we go on with this now ?...
For `nn_send`, we could start by just exposing a non-blocking version of `write`. I quite don't see how to integrate `nn_allocmsg` correctly for the moment. For `nn_recv`, there are four...
Since some public parts (Reader, Writer, Duration ...) of nanomsg.rs won't make it in Rust 1.0, we will probably end up with a branch for the Rust 1.0 and another...
Since the inner value is a numeric id, it could be useful when debugging.
The rust nightly build cc19e3380 2014-12-20 introduced the warning reproduced below. This drew my attention to the fact this conflicting lifetime name wasn't even used in the function ! So...
Is there a way to provide nn_recv the native buffer used by a Vec[u8], to avoid the copy ?
The native nanomsg lib has quite a lot of constants for the errors, and they should be reported to the nanomsg.rs users. The [nn_errno](http://nanomsg.org/v0.4/nn_errno.3.html) and [nn_strerror](http://nanomsg.org/v0.4/nn_strerror.3.html) should be used internally...
The users should be able to get or set a socket option without having to browse the option constant list and without being forced to do any unsafe pointer manipulation.