Skip to content
This repository was archived by the owner on Jun 16, 2025. It is now read-only.

Commit b6156e4

Browse files
committed
Update documentation: clarify motivation for abandoning colored functions and enhance section title for colored functions
1 parent 6cd9578 commit b6156e4

File tree

2 files changed

+4
-1
lines changed

2 files changed

+4
-1
lines changed

basic.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1035,6 +1035,9 @@ Its main purpose is to provide a space for resource control that affects all cor
10351035
10361036
Resource control at the top level is a useful tool for organizing applications, frameworks, and libraries.
10371037
1038+
> Thus, the desire to abandon colored functions is the main motivation for implementing `Scope`.
1039+
> **Colored functions** allow Scope to be avoided altogether, as each coroutine would act as a `Scope` for its children.
1040+
10381041
#### Point of Responsibility
10391042
10401043
The `spawn <callable>` expression allows you to create coroutines,

colored_functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Colored Functions
1+
# How colored functions help implement structured concurrency
22

33
Consider the following code:
44

0 commit comments

Comments
 (0)