futures-macro

Zero-cost asynchronous programming in Rust

Latest version: 0.3.25 registry icon
Maintenance score
100
Safety score
100
Popularity score
100
Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.
Security
  Vulnerabilities
Version Suggest Low Medium High
0.3.25 0 0 0 0
0.3.24 0 0 0 0
0.3.23 0 0 0 0
0.3.22 0 0 0 0
0.3.21 0 0 0 0
0.3.20 0 0 0 0
0.3.19 0 0 0 0
0.3.18 0 0 0 0
0.3.17 0 0 0 0
0.3.16 0 0 0 0
0.3.15 0 0 0 0
0.3.14 0 0 0 0
0.3.13 0 0 0 0
0.3.12 0 0 0 0
0.3.11 0 0 0 0
0.3.10 0 0 0 0
0.3.9 0 0 0 0
0.3.8 0 0 0 0
0.3.7 0 0 0 0
0.3.6 0 0 0 0
0.3.5 0 0 0 0
0.3.4 0 0 0 0
0.3.3 0 0 0 0
0.3.2 0 0 0 0
0.3.1 0 0 0 0
0.3.0 0 0 0 0

Stability
Latest release:

0.3.25 - this version is safe to use because it has no known security vulnerabilities at this time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

Apache-2.0   -   Apache License 2.0

Not a wildcard

Not proprietary

OSI Compliant


MIT   -   MIT License

Not a wildcard

Not proprietary

OSI Compliant



futures-rs

Zero-cost asynchronous programming in Rust

Build Status Crates.io

Documentation | Website

futures-rs is a library providing the foundations for asynchronous programming in Rust. It includes key trait definitions like Stream, as well as utilities like join!, select!, and various futures combinator methods which enable expressive asynchronous control flow.

Usage

Add this to your Cargo.toml:

[dependencies]
futures = "0.3"

The current futures requires Rust 1.45 or later.

Feature std

Futures-rs works without the standard library, such as in bare metal environments. However, it has a significantly reduced API surface. To use futures-rs in a #[no_std] environment, use:

[dependencies]
futures = { version = "0.3", default-features = false }

License

Licensed under either of Apache License, Version 2.0 or MIT license at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.