futures-rs VS node_crunch

So this is actually better than true fairness (true fairness would lead to deadlock if a sender is forgotten). It is a pity that the there does not seem to be resources that document this design. There is this old thread where Carl provides some background, but I found it personally a bit hard to follow.

Is this still true after it switched to using FuturesOrdered?

Done.

You can use Streams, which are the async version of Iterators; They aren't stable yet, so you'll have to use a crate such as futures.

futures

For traits, like AsyncRead and AsyncWrite, go with the futures crate.

Here is the PR: https://github.com/rust-lang/futures-rs/pull/2551

Yield = wake the `waker_ref`. Avoiding the yield would be clone().wake().

That said, "poll immediately" isn't actually a thing nor was it ever a thing except in incorrect implementations.

Rust lacks an implementation of ReactiveX. futures/futures-signals seems to be the the ecosystem equivalent but I'm sure there'd be a lot of interest in an actual implementation.

The opposite problem exists as well. Many types are actually unwind safe, but do not get the autotrait. In that case authors would have to manually declare them UnwindSafe. Because this is rarely done, having an API with a trait bound T: UnwindSafe is rarely viable in terms of ergonomics. It now obliges client code to wrap all calls to your API in AssertUnwindSafe which, if they use types from third party libraries, obliges them to assert this is fine. example

Also, we plan to give users more control in the future. See https://github.com/rust-lang/futures-rs/issues/2207, https://github.com/rust-lang/futures-rs/issues/2295, etc. for this

I've written my own crate called node-crunch for distributed computing.

This looks really nice! It has encryption and compression is planned for the next release. I've developed node_crunch, a crate for distributed computing and designed the protocols myself. I think that Zenoh could make my life a lot easier ;-) I'll definitely try it out!

You may be interested in darwin-rs, a crate for evolutionary algorithm that I'm working on. It uses multiple threads to speed things up, but I'm currently implementing node-crunch support, so that it can run on a cluster.

Nice! I'm currently working on node_crunch a crate for distributed computing. I've modified an existing ray tracer to run on a cluster. If you're interested you can have a look at the code.

I'm currently working on node_crunch.