Fix todo
This commit is contained in:
parent
19aa126025
commit
baf44f8627
|
@ -329,7 +329,9 @@ and uses the cache otherwise. We choose this route.
|
||||||
variables above a given variable before evaluating the variable
|
variables above a given variable before evaluating the variable
|
||||||
itself. So, each function will first call (and therefore
|
itself. So, each function will first call (and therefore
|
||||||
{{< sidenote "right" "force-note" "force" >}}
|
{{< sidenote "right" "force-note" "force" >}}
|
||||||
{{< todo >}}Explain forcing{{< /todo >}}
|
Forcing, in this case, comes from the context of lazy evaluation. To
|
||||||
|
force a variable or an expression is to tell the program to compute its
|
||||||
|
value, even though it may have been putting it off.
|
||||||
{{< /sidenote >}}) the functions
|
{{< /sidenote >}}) the functions
|
||||||
generated for variables declared above the function's own variable.
|
generated for variables declared above the function's own variable.
|
||||||
5. To keep track of all of this, we use the already-existing state monad
|
5. To keep track of all of this, we use the already-existing state monad
|
||||||
|
|
Loading…
Reference in New Issue
Block a user