From a2367b4d937bde0be0fa39518d7b928ceda4f8e4 Mon Sep 17 00:00:00 2001 From: Martin Geisler Date: Mon, 24 Jul 2023 20:17:23 +0200 Subject: [PATCH] Use `* foo:` for list (#1025) We could use an m-dash, but we're using `:` aligns with how the rest of the course is written. --- src/async/runtimes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/async/runtimes.md b/src/async/runtimes.md index 22a70621..9d2888aa 100644 --- a/src/async/runtimes.md +++ b/src/async/runtimes.md @@ -4,12 +4,12 @@ A *runtime* provides support for performing operations asynchronously (a *reactor*) and is responsible for executing futures (an *executor*). Rust does not have a "built-in" runtime, but several options are available: - * [Tokio](https://tokio.rs/) - performant, with a well-developed ecosystem of + * [Tokio](https://tokio.rs/): performant, with a well-developed ecosystem of functionality like [Hyper](https://hyper.rs/) for HTTP or [Tonic](https://github.com/hyperium/tonic) for gRPC. - * [async-std](https://async.rs/) - aims to be a "std for async", and includes a + * [async-std](https://async.rs/): aims to be a "std for async", and includes a basic runtime in `async::task`. - * [smol](https://docs.rs/smol/latest/smol/) - simple and lightweight + * [smol](https://docs.rs/smol/latest/smol/): simple and lightweight Several larger applications have their own runtimes. For example, [Fuchsia](https://fuchsia.googlesource.com/fuchsia/+/refs/heads/main/src/lib/fuchsia-async/src/lib.rs)