aboutsummaryrefslogtreecommitdiff
path: root/embassy-sync/src/priority_channel.rs
diff options
context:
space:
mode:
authorOliver Rockstedt <[email protected]>2024-05-22 00:54:52 +0200
committerOliver Rockstedt <[email protected]>2024-05-22 00:54:52 +0200
commitaee9d5902a4feb4a5fbb8d0e719401c96f3f651e (patch)
treed40e4bd76bf8616b337579f36488f9a8c1c7656f /embassy-sync/src/priority_channel.rs
parent68e784ccd6e17a2fa4dc837a6eb46b2ff93504d5 (diff)
embassy-sync: fixed some documentation typos
Diffstat (limited to 'embassy-sync/src/priority_channel.rs')
-rw-r--r--embassy-sync/src/priority_channel.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/embassy-sync/src/priority_channel.rs b/embassy-sync/src/priority_channel.rs
index 8572d3608..2954d1b76 100644
--- a/embassy-sync/src/priority_channel.rs
+++ b/embassy-sync/src/priority_channel.rs
@@ -335,7 +335,7 @@ where
335/// buffer is full, attempts to `send` new messages will wait until a message is 335/// buffer is full, attempts to `send` new messages will wait until a message is
336/// received from the channel. 336/// received from the channel.
337/// 337///
338/// Sent data may be reordered based on their priorty within the channel. 338/// Sent data may be reordered based on their priority within the channel.
339/// For example, in a [`Max`](heapless::binary_heap::Max) [`PriorityChannel`] 339/// For example, in a [`Max`](heapless::binary_heap::Max) [`PriorityChannel`]
340/// containing `u32`'s, data sent in the following order `[1, 2, 3]` will be received as `[3, 2, 1]`. 340/// containing `u32`'s, data sent in the following order `[1, 2, 3]` will be received as `[3, 2, 1]`.
341pub struct PriorityChannel<M, T, K, const N: usize> 341pub struct PriorityChannel<M, T, K, const N: usize>