moro icon indicating copy to clipboard operation
moro copied to clipboard

Experiments with structured concurrency in Rust

Results 4 moro issues
Sort by recently updated
recently updated
newest added

I completely don't understand why I should use moro as opposed to plain futures (not to be confused to tasks). README shows code example, but I can write similar example...

This adds "local" versions of the macro and scope functions to support non-Send Futures.

Would you be open to a PR that puts unstable features behind a `nightly` feature flag so this crate can be used on stable?

> https://docs.rs/moro/latest/moro/macro.async_scope.html > To avoid this, use the `infallible` method on the scope to convert it into a non-cancellable scope: > `let scope = moro::async_scope!(|scope| {/* ... */}).await;` Looks like...