Crates.io | tokio-file |
lib.rs | tokio-file |
version | |
source | src |
created_at | 2017-07-26 03:34:41.30414+00 |
updated_at | 2025-04-19 19:26:51.907929+00 |
description | Asynchronous file I/O for Tokio |
homepage | |
repository | https://github.com/asomers/tokio-file |
max_upload_size | |
id | 25103 |
Cargo.toml error: | TOML parse error at line 25, column 1 | 25 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
A library for integrating file I/O with tokio. File I/O can be seamlessly mixed with all other Future types within the Tokio reactor.
# Cargo.toml
[depdendencies]
tokio = "1.0.0"
tokio-file = "0.10.0"
See the examples
directory in the repository. In general, any program that's
already using tokio
can add file I/O by using tokio_file::AioFileExt
and
running the resulting futures in the tokio reactor.
tokio-file
version 0.10 works on FreeBSD, using the mio-aio
crate. It will
probably also work on DragonflyBSD and OSX. It does not work on Linux. The
tokio-file
API can be supported on Linux, but it will need a completely
different backend. Instead of using POSIX AIO as mio-aio
does, Linux will
need a mio-libaio
crate, that uses Linux's nonstandard libaio with an eventfd
for notifications. That's the approach taken by seastar.
tokio-file
is primarily distributed under the terms of both the MIT license
and the Apache License (Version 2.0).
See LICENSE-APACHE, and LICENSE-MIT for details.