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: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,7 +100,7 @@ do e <- liftEff' myExcFunc
100
100
liftEff $ either (const $ trace "Oh noes!") (const $ trace "Yays!") e
101
101
```
102
102
103
-
## Failure
103
+
## Dealing with Failure
104
104
105
105
The `Aff` monad has error handling baked in, so ordinarily you don't have to worry about it.
106
106
@@ -150,7 +150,7 @@ block the current thread of execution:
150
150
forkAff myAff
151
151
```
152
152
153
-
Because Javascript is single-threaded, forking does not actually cause the computation to be run in a separate thread, it merely means the subsequent chain of computations will be executed without first waiting for the forked computation to complete.
153
+
Because Javascript is single-threaded, forking does not actually cause the computation to be run in a separate thread. Forking just allows the subsequent actions to execute without waiting for the forked computation to complete.
154
154
155
155
## Variables
156
156
@@ -159,9 +159,9 @@ be used as low-level building blocks for asynchronous programs.
0 commit comments