From cc1e7154fce6780b8db7fe3457405b8e02563f7d Mon Sep 17 00:00:00 2001 From: Nils Fitinghoff Date: Tue, 29 Aug 2023 09:28:43 +0200 Subject: book: Update default priority to 0 --- book/en/src/by-example/software_tasks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'book/en/src/by-example/software_tasks.md') diff --git a/book/en/src/by-example/software_tasks.md b/book/en/src/by-example/software_tasks.md index 444f4a6..756150d 100644 --- a/book/en/src/by-example/software_tasks.md +++ b/book/en/src/by-example/software_tasks.md @@ -35,7 +35,7 @@ $ cargo run --target thumbv7m-none-eabi --example spawn ``` You may `spawn` a *software* task again, given that it has run-to-completion (returned). -In the below example, we `spawn` the *software* task `foo` from the `idle` task. Since the default priority of the *software* task is 1 (higher than `idle`), the dispatcher will execute `foo` (preempting `idle`). Since `foo` runs-to-completion. It is ok to `spawn` the `foo` task again. +In the below example, we `spawn` the *software* task `foo` from the `idle` task. Since the priority of the *software* task is 1 (higher than `idle`), the dispatcher will execute `foo` (preempting `idle`). Since `foo` runs-to-completion. It is ok to `spawn` the `foo` task again. Technically the async executor will `poll` the `foo` *future* which in this case leaves the *future* in a *completed* state. -- cgit v1.2.3