summaryrefslogtreecommitdiffstats
path: root/README.md
AgeCommit message (Collapse)Author
2020-11-03chore: update CI badge (#3091)Carl Lerche
2020-10-26readme: update the MSRV to 1.45 (#3048)nickelc
2020-07-24doc: feature flags in README (#2682)Blas Rodriguez Irizar
2020-07-22doc: fix links to new website (#2674)Alice Ryhl
2020-07-21doc: update links in README.md and CONTRIBUTING.md (#2609)Alice Ryhl
2020-04-03doc: Fix readme link (#2370)nasa
2020-02-22tokio: fix broken contributing guide link (#2267)Thomas
The link to the contributing guide in the tokio sub crate was referencing a non-existent file. This updates the link to reference the repo root's CONTRIBUTING.md file. Fixes: #2266
2020-02-11Correct link to the guide on tokio.rs (#2229)Wade Mealing
The current link to tokio.rs/docs 404's. This change redirects the "guides" link to the docs overview (which may be what was intended).
2020-01-21readme: Add more related tokio projects (#2128)Lucio Franco
2020-01-09chore: update Tokio discord url (#2086)Lucio Franco
2020-01-07doc: fix old notes regarding examples and async/await (#2071)Alice Ryhl
2019-12-18Fix ROADMAP link (#1981)Dmitrii Goriunov
2019-12-16chore: add roadmap (#1965)Kelly Thomas Kline
2019-12-11chore: fix the outdated example in README (#1930)nickelc
2019-11-27doc: misc API documentation fixes (#1834)Oleg Nosov
2019-11-26chore: replace Gitter badge with Discord (#1828)Artem Vorotnikov
2019-11-26chore: remove updating note from readme (#1824)Carl Lerche
2019-11-23tokio: remove performance regression notice (#1817)leo-lb
2019-11-22default all feature flags to off (#1811)Carl Lerche
Changes the set of `default` feature flags to `[]`. By default, only core traits are included without specifying feature flags. This makes it easier for users to pick the components they need. For convenience, a `full` feature flag is included that includes all components. Tests are configured to require the `full` feature. Testing individual feature flags will need to be moved to a separate crate. Closes #1791
2019-10-22codec: move into tokio-util (#1675)Carl Lerche
Related to #1318, Tokio APIs that are "less stable" are moved into a new `tokio-util` crate. This crate will mirror `tokio` and provide additional APIs that may require a greater rate of breaking changes. As examples require `tokio-util`, they are moved into a separate crate (`examples`). This has the added advantage of being able to avoid example only dependencies in the `tokio` crate.
2019-10-21fs: move into `tokio` (#1672)Carl Lerche
A step towards collapsing Tokio sub crates into a single `tokio` crate (#1318). The `fs` implementation is now provided by the main `tokio` crate. The `fs` functionality may still be excluded from the build by skipping the `fs` feature flag.
2019-09-17Update README.md (#1545)yjh
change url's `version` to `latest`.
2019-09-13chore: add stability note to readme. (#1554)Carl Lerche
2019-08-30chore: fix compile error on latest nightly (#1512)kellerkindt
2019-08-20chore: bump to newer nightly (#1485)Taiki Endo
2019-08-17chore: prepare 0.2.0-alpha.2 release (#1465)Carl Lerche
2019-08-16uds: move into tokio-net (#1462)Carl Lerche
2019-08-16udp: remove files left over from moving tokio-udp (#1461)Carl Lerche
2019-08-15tcp: move tokio-tcp into tokio-net (#1456)Carl Lerche
2019-08-15threadpool: move threadpool into tokio-executor (#1452)Carl Lerche
The threadpool is behind a feature flag. Refs: #1264
2019-08-15reactor: rename tokio-reactor -> tokio-net (#1450)Carl Lerche
* reactor: rename tokio-reactor -> tokio-net This is in preparation for #1264
2019-08-08chore: prepare for v0.2.0-alpha.1 release (#1410)Lucio Franco
2019-08-06tokio: fix API doc examples (#1396)Carl Lerche
2019-07-19chore: remove tokio-futures facade crate (#1327)Carl Lerche
This switches from using the tokio-futures facade to referencing futures-* crates directly.
2019-07-15chore: indicate the master branch docs are old. (#1304)Carl Lerche
Fixes #1292
2019-07-09chore: Add link to docs (#1276)Gurwinder Singh
2019-07-08chore: update examples link in README (#1274)Carl Lerche
2019-07-03Add missing links in README.md (#1233)Thomas Lacroix
Fixes: #1229
2019-06-29docs: add note in the readme about the master branch (#1230)Lucio Franco
2019-06-28chore: remove `tokio-trace`, add "Related Projects" to README (#1221)Eliza Weisman
## Motivation The `tokio-trace` and `tokio-trace-core` crates have been renamed to `tracing` and `tracing-core`, and moved to their own repository (`tokio-rs/tracing`). ## Solution This branch removes `tokio-trace` and `tokio-trace-core` from the `tokio` repository. In addition, I've added a "Related Projects" section to the root README, which lists `tracing` (as well as `mio`, and `bytes`) as other libraries maintained by the Tokio project. I thought that this would help folks looking for `tokio-trace` here find it in its new home. In addition, it changes `tokio` to depend on `tracing-core` rather than `tokio-trace-core`. Closes #1159 Signed-off-by: Eliza Weisman <eliza@buoyant.io>
2019-05-14Merge branch 'v0.1.x'Carl Lerche
2019-05-14Release tokio v0.1.20, tokio-timer v0.2.21, and remove async-await-preview ↵Carl Lerche
feature. (#1089) The `async-await-preview` feature is removed as 0.1 will no longer track Rust nightly. This also bumps: - tokio-timer (0.2.11).
2019-05-14Update Tokio to Rust 2018 (#1082)Carl Lerche
2019-04-27Fix an error in the mit-url in the README.md (#1068)Ian Hamlin
2019-04-25Async/await polish (#1058)Carl Lerche
A general refresh of Tokio's experimental async / await support.
2019-04-22Bump `tokio` to 0.1.19. (#1053)Carl Lerche
This also bumps: - tokio-async-await (0.1.7) - tokio-buf (0.1.1) - tokio-sync (0.1.5) - tokio-threadpool (0.1.14)
2019-03-22chore: Fix examples not working with `cargo run` (#998)Eliza Weisman
* chore: Fix examples not working with `cargo run` ## Motivation PR #991 moved the `tokio` crate to its own subdirectory, but did not move the `examples` directory into `tokio/examples`. While attempting to use the examples for testing another change, I noticed that #991 had broken the ability to use `cargo run`, as the examples were no longer considered part of a crate that cargo was aware of: ``` tokio on master [$] via 🦀v1.33.0 at ☸️ aks-eliza-dev ➜ cargo run --example chat error: no example target named `chat` Did you mean `echo`? ``` ## Solution This branch moves the examples into the `tokio` directory, so cargo is now once again aware of them: ``` tokio on eliza/fix-examples [$] via 🦀v1.33.0 at ☸️ aks-eliza-dev ➜ cargo run --example chat Compiling tokio-executor v0.1.7 (/Users/eliza/Code/tokio/tokio-executor) Compiling tokio-reactor v0.1.9 Compiling tokio-threadpool v0.1.13 Compiling tokio-current-thread v0.1.6 Compiling tokio-timer v0.2.10 Compiling tokio-uds v0.2.5 Compiling tokio-udp v0.1.3 Compiling tokio-tcp v0.1.3 Compiling tokio-fs v0.1.6 Compiling tokio v0.1.18 (/Users/eliza/Code/tokio/tokio) Finished dev [unoptimized + debuginfo] target(s) in 7.04s Running `target/debug/examples/chat` server running on localhost:6142 ``` Signed-off-by: Eliza Weisman <eliza@buoyant.io> Signed-off-by: Eliza Weisman <eliza@buoyant.io>
2019-03-22Bump Tokio version to v0.1.18 (#997)Carl Lerche
Also bumps: - tokio-signal (0.2.8) - tokio-current-thread (0.1.6) - tokio-executor (0.1.7) - tokio-threadpool (0.1.13) [ci-release]
2019-03-13Bump Tokio to v0.1.17 (#983)Carl Lerche
Also bumps: - tokio-sync (v0.1.4)
2019-03-01Bump Tokio to 0.1.16. (#941)Carl Lerche
Also bumps: * tokio-current-thread (0.1.5) * tokio-fs (0.1.6) * tokio-io (0.1.12) * tokio-reactor (0.1.9) * tokio-threadpool (0.1.12)