From 1e44ee76431b910c61bd330fe22d51070dab3507 Mon Sep 17 00:00:00 2001 From: tower120 Date: Sun, 10 Nov 2024 04:07:35 +0200 Subject: [PATCH] v0.2.0 --- Cargo.toml | 2 +- examples/mpmc.rs | 2 +- src/lib.rs | 6 +++--- src/reader.rs | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/Cargo.toml b/Cargo.toml index f5a41c7..61addb8 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "chute" -version = "0.1.1" +version = "0.2.0" license = "MIT OR Apache-2.0" edition = "2021" exclude = ["benchmarks", "doc"] diff --git a/examples/mpmc.rs b/examples/mpmc.rs index d939aba..bdda990 100644 --- a/examples/mpmc.rs +++ b/examples/mpmc.rs @@ -18,7 +18,7 @@ fn main() { s.spawn(move || { let mut sum = 0; for _ in 0..MESSAGES { - // Wait for ths next message. + // Wait for the next message. let msg = loop { if let Some(msg) = reader.next() { break msg; diff --git a/src/lib.rs b/src/lib.rs index ea6380c..88d9922 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -14,9 +14,9 @@ //! //! In general, using `Arc>>` is more performant //! than `Arc>` from writer perspective. -//! But! Writing simultaneously from several threads is faster with [mpmc]. -//! -//! Read performance identical. +//! But! Writing simultaneously from several threads is much faster with [mpmc]. +//! +//! The read performance is almost equal, with a slight advantage for [spmc]. //! //! # Order //! diff --git a/src/reader.rs b/src/reader.rs index 7f90c1c..e775dcd 100644 --- a/src/reader.rs +++ b/src/reader.rs @@ -5,7 +5,7 @@ /// with message BEFORE consuming the next one. /// Because of this, it does not implement [Iterator]. But [ClonedReader] does. /// -/// We expect it to be mainly used with reader in this way: +/// We expect it to be mainly used in this way: /// ``` /// # let queue: chute::spmc::Queue = Default::default(); /// # let mut reader = queue.reader();