mirror of
https://github.com/tokio-rs/tokio.git
synced 2026-08-22 00:00:11 +02:00
task: fix documentation links (#6336)
This commit is contained in:
+5
-1
@@ -1,4 +1,4 @@
|
||||
279
|
||||
283
|
||||
&
|
||||
+
|
||||
<
|
||||
@@ -59,6 +59,7 @@ combinators
|
||||
config
|
||||
Config
|
||||
connectionless
|
||||
coroutines
|
||||
cpu
|
||||
cpus
|
||||
Customizable
|
||||
@@ -92,6 +93,7 @@ enqueued
|
||||
EntryInner
|
||||
enum
|
||||
eof
|
||||
Erlang's
|
||||
errored
|
||||
EWMA
|
||||
expirations
|
||||
@@ -109,6 +111,7 @@ fs
|
||||
functionalities
|
||||
getters
|
||||
GID
|
||||
goroutines
|
||||
Growable
|
||||
gzip
|
||||
hashmaps
|
||||
@@ -132,6 +135,7 @@ IP
|
||||
IPv4
|
||||
IPv6
|
||||
iteratively
|
||||
Kotlin's
|
||||
latencies
|
||||
Lauck
|
||||
libc
|
||||
|
||||
@@ -5,8 +5,8 @@
|
||||
//! A _task_ is a light weight, non-blocking unit of execution. A task is similar
|
||||
//! to an OS thread, but rather than being managed by the OS scheduler, they are
|
||||
//! managed by the [Tokio runtime][rt]. Another name for this general pattern is
|
||||
//! [green threads]. If you are familiar with [`Go's goroutines`], [`Kotlin's
|
||||
//! coroutines`], or [`Erlang's processes`], you can think of Tokio's tasks as
|
||||
//! [green threads]. If you are familiar with [Go's goroutines], [Kotlin's
|
||||
//! coroutines], or [Erlang's processes], you can think of Tokio's tasks as
|
||||
//! something similar.
|
||||
//!
|
||||
//! Key points about tasks include:
|
||||
|
||||
Reference in New Issue
Block a user