Nanomsg looks interesting and I'll take a closer look. But I'm interested
in a pure rust implementation of async messaging because I'd like to create
an embedded OS using rust and not use C if possible.
I been thinking about the problem and one of the questions I have is how to
transfer ownership
Hi,
On Mon, Sep 29, 2014 at 11:01 PM, Wink Saville w...@saville.com wrote:
Nanomsg looks interesting and I'll take a closer look. But I'm interested in
a pure rust implementation of async messaging because I'd like to create an
embedded OS using rust and not use C if possible.
I think even
On Mon, Sep 29, 2014 at 1:01 PM, Wink Saville w...@saville.com wrote:
Nanomsg looks interesting and I'll take a closer look. But I'm interested
in a pure rust implementation of async messaging because I'd like to create
an embedded OS using rust and not use C if possible
You might take a look
On Mon, Sep 29, 2014 at 1:10 PM, Paul Colomiets p...@colomiets.name wrote:
Hi,
On Mon, Sep 29, 2014 at 11:01 PM, Wink Saville w...@saville.com wrote:
Nanomsg looks interesting and I'll take a closer look. But I'm
interested in
a pure rust implementation of async messaging because I'd like
These are the semantics of a boxed value.
On Mon, Sep 29, 2014 at 9:47 PM, Wink Saville w...@saville.com wrote:
On Mon, Sep 29, 2014 at 1:10 PM, Paul Colomiets p...@colomiets.name wrote:
Hi,
On Mon, Sep 29, 2014 at 11:01 PM, Wink Saville w...@saville.com wrote:
Nanomsg looks interesting
Cool, I've been following capn proto and have used protobufs a little. This
is the direction of what I'm thinking and I'm wondering if the rust notion
of
ownership can be leveraged in message passing. Hence my silly questions.
On Mon, Sep 29, 2014 at 2:03 PM, Tony Arcieri basc...@gmail.com wrote:
Perfect!
On Mon, Sep 29, 2014 at 9:50 PM, Clark Gaebel cg.wowus...@gmail.com wrote:
These are the semantics of a boxed value.
On Mon, Sep 29, 2014 at 9:47 PM, Wink Saville w...@saville.com wrote:
On Mon, Sep 29, 2014 at 1:10 PM, Paul Colomiets p...@colomiets.name
wrote:
Hi,
On
I'd like to have one API which would allow sending/receiving messages
asynchronously, safely and efficiently over any transport and should work
for components that run in the same thread, different threads, different
processes or between devices which might be connected via any arbitrary
