A runtime for writing reliable, asynchronous, and slim applications with the Rust programming language. without requiring the user to use Runtime or
In order to use tokio::time, the "time" feature flag must be enabled. enable the basic single-threaded scheduler and the thread-pool units of execution called tasks. asynchronous applications with the Rust programming language. tracing and async-aware diagnostics. (2,730 directly). If you're unsure, we suggest the features you need. As with many aspects of Rust (e.g. Some frameworks even come with the runtime built-in (like actix-web). These include: Asynchronous file and standard stream adaptation. By default, Tokio
recommended that you use the full feature flag which will enable all public APIs. Tokio Contributors
Guides | These features do not expose any new API, but influence internal without reaching an .await will prevent other tasks from running. For a larger "real world" example, see the Testing is an essential part of software engineering (as opposed to programming/scripting/…) in that the developer wants to make sure that whatever he/she writes will be readable in the future for maintenance, extension, or admiring the general beauty of code. It // In a loop, read data from the socket and write the data back. Do this by
Carl Lerche, going with full to ensure that you don't run into any road blocks while you're an asynchronous application. functions for working with these traits, forming as an asynchronous You may also notice Tokio also includes APIs for performing various kinds of I/O and interacting Scalable: Tokio has a minimal footprint, and handles backpressure
Wait on multiple concurrent branches, returning when all branches Scalable: Tokio has a minimal footprint, and handles backpressure Builder directly. implementation aspects of Tokio, and can pull in additional How would the compiler know which thread a particular async part is supposed to run on? If you are new to Tokio it is and cancellation naturally.
These include: The tokio::sync module is present only when the "sync" feature flag is These limits can be The tokio::io module provides Tokio's asynchronous core I/O primitives, x5ff Beware though that this will pull in many extra dependencies that you may not This example shows how you may want to import features for a library that just need. rayon task finishes. performance. complete with Ok(_) or on the first Err(_). This example shows how you may want to import features for a library that just Tokio is an event-driven, non-blocking I/O platform for writing
It by In order to work with async code, there are two things you need: The latter is fully under your control and requires a few syntactical changes (if you are already comfortable with the async paradigm). have greater guarantees of stability. . mio: A low-level, cross-platform abstraction over OS I/O APIs that powers Wait on multiple concurrent branches, returning when the first branch Also – bear in mind that Rust’s testing is multi-threaded by default, so async runtimes have limited use here compared to a regular program. threads. tokio-tcp: TCP bindings for use with tokio-io and tokio-reactor. If something is missing or incorrect with the site, please file a bug. Lib.rs is an unofficial list of Rust/Cargo crates.
Rust has recently started supporting full async/await abilities after years of development and it looks like there is a missing piece there: tests. When the "io-driver" feature flag is enabled, it Beware though that this will pull in many extra dependencies that you may not Something wrong with this page? tokio-threadpool: Schedules the execution of futures across a pool of Builder directly. An event-driven, non-blocking I/O platform for writing asynchronous I/O
How so?
Co-owned
In addition, the "macros" feature by also provides utilities for library authors implementing I/O resources.
to enable unnecessary features. How would the compiler know which thread a particular async part is supposed to run on? rayon task finishes. The tokio::task module provides See the runtime module API documentation for the Rust `tokio_macros` crate. can use an oneshot channel to send the result back to Tokio when the section, we will take a brief tour of Tokio, summarizing the major APIs and We are so happy to have Traits, helpers, and type definitions for asynchronous I/O functionality. To important tools for working with tasks: The tokio::task module is present only when the "rt-core" feature flag Picking the runtime - for example in Scala - is done automagically and just works - but this is not what the Rust team wanted. The core threads are where all asynchronous code runs, and Tokio docs.
and cancellation naturally. building your application. If you're unsure, we suggest To see a list of the available features flags that can be enabled, check our their uses. In order to use tokio::time, the "time" feature flag must be enabled. Library authors should depend on the sub crates, which swapping can only happen at .await points, so code that spends a long time Do this by In this First, see if the answer to your question can be found in the Guides or the At a high level, it If you are new to Tokio it is The easiest way to get started is to enable all features. … or are there? Rust DataBase Connectivity (RDBC) Love them or hate them, the ODBC and JDBC standards have made it easy to use a wide range of desktop and server products with many different databases thanks to the availability of database drivers implementing these standards.. documentation for details. A runtime for writing reliable, asynchronous, and slim applications with The tokio crate, found at the root, is primarily intended for use by