From db6929ad62a1cebb088d7b5c5c16d689c49449b9 Mon Sep 17 00:00:00 2001 From: Val Lorentz Date: Sun, 11 Feb 2024 15:08:01 +0100 Subject: [PATCH] task: fix documentation links (#6336) --- spellcheck.dic | 6 +++++- tokio/src/task/mod.rs | 4 ++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/spellcheck.dic b/spellcheck.dic index ea73532af..5a0745df3 100644 --- a/spellcheck.dic +++ b/spellcheck.dic @@ -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 diff --git a/tokio/src/task/mod.rs b/tokio/src/task/mod.rs index 806b9aebe..f45df10a9 100644 --- a/tokio/src/task/mod.rs +++ b/tokio/src/task/mod.rs @@ -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: