You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _site/0-book/unit-6/section-1/0-null.md
+13-4Lines changed: 13 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ These examples illustrate that "absence," "emptiness," or "nullity" is not merel
24
24
25
25
## 2. The Theoretical Pillar: From Function Pipelines to Algebraic Structures (A Revisit)
26
26
27
-
Before diving into the core of the "absence" debate, we must return to the theoretical pillar of this book. This is the deliberate, logical flow, established in Unit 2, of how the definition of an **"algebraic structure"** is naturally derived from the idea of a **"function pipeline."
27
+
Before diving into the core of the "absence" debate, we must return to the theoretical pillar of this book. This is the deliberate, logical flow, established in Unit 2, of how the definition of an **"algebraic structure"** is naturally derived from the idea of a **"function pipeline."**
28
28
29
29
First, our starting point is the fundamental concept in functional programming: the "pipeline," where data flows through a series of functions.
30
30
@@ -202,13 +202,22 @@ We position this approach as a **theoretically valid path** that consciously div
Copy file name to clipboardExpand all lines: _site/0-book/unit-6/section-2/0-bind-chain.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,13 +58,16 @@ step0.define(Now, "Hello!");
58
58
This `Timeline``bind` chain is similar to `Promise.then` in many ways.
59
59
60
60
***Sequential Execution**: The next operation starts after the previous one is complete.
61
-
***Value Passing**: The result of the previous step is passed to the next step.
61
+
62
+
***Value Passing**: The result of the previous step is passed to the next step.
62
63
63
64
However, there are also important differences in the fundamental approach.
64
65
65
66
***Reactive**: `Timeline` is a reactive system that automatically triggers subsequent operations in response to value changes.
66
-
***Explicit Receiving Timeline**: You need to pre-define a dedicated `Timeline` to receive the result of each step.
67
-
***Synchronous Return Value**: The `bind` function itself must **synchronously** return the `Timeline` to wait for next, without waiting for the asynchronous operation to complete.
67
+
68
+
***Explicit Receiving Timeline**: You need to pre-define a dedicated `Timeline` to receive the result of each step.
69
+
70
+
***Synchronous Return Value**: The `bind` function itself must **synchronously** return the `Timeline` to wait for next, without waiting for the asynchronous operation to complete.
Copy file name to clipboardExpand all lines: src/content/docs/en/book/unit-6/section-1/0-null.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ These examples illustrate that "absence," "emptiness," or "nullity" is not merel
32
32
33
33
## 2. The Theoretical Pillar: From Function Pipelines to Algebraic Structures (A Revisit)
34
34
35
-
Before diving into the core of the "absence" debate, we must return to the theoretical pillar of this book. This is the deliberate, logical flow, established in Unit 2, of how the definition of an **"algebraic structure"** is naturally derived from the idea of a **"function pipeline."
35
+
Before diving into the core of the "absence" debate, we must return to the theoretical pillar of this book. This is the deliberate, logical flow, established in Unit 2, of how the definition of an **"algebraic structure"** is naturally derived from the idea of a **"function pipeline."**
36
36
37
37
First, our starting point is the fundamental concept in functional programming: the "pipeline," where data flows through a series of functions.
Copy file name to clipboardExpand all lines: src/content/docs/en/book/unit-6/section-2/0-bind-chain.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,13 +67,16 @@ step0.define(Now, "Hello!");
67
67
This `Timeline``bind` chain is similar to `Promise.then` in many ways.
68
68
69
69
***Sequential Execution**: The next operation starts after the previous one is complete.
70
-
***Value Passing**: The result of the previous step is passed to the next step.
70
+
71
+
***Value Passing**: The result of the previous step is passed to the next step.
71
72
72
73
However, there are also important differences in the fundamental approach.
73
74
74
75
***Reactive**: `Timeline` is a reactive system that automatically triggers subsequent operations in response to value changes.
75
-
***Explicit Receiving Timeline**: You need to pre-define a dedicated `Timeline` to receive the result of each step.
76
-
***Synchronous Return Value**: The `bind` function itself must **synchronously** return the `Timeline` to wait for next, without waiting for the asynchronous operation to complete.
76
+
77
+
***Explicit Receiving Timeline**: You need to pre-define a dedicated `Timeline` to receive the result of each step.
78
+
79
+
***Synchronous Return Value**: The `bind` function itself must **synchronously** return the `Timeline` to wait for next, without waiting for the asynchronous operation to complete.
0 commit comments