Skip to content

Commit 7364688

Browse files
author
Elvis Stansvik
committed
Avoid repetition in visibility explanation
The "each local scope can also see all the local scopes that contain it" occurred twice. I kept the second occurrance.
1 parent d3ebba9 commit 7364688

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

03_functions.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -207,12 +207,10 @@ The code inside the `ingredient` function can see the `factor` binding
207207
from the outer function. But its local bindings, such as `unit` or
208208
`ingredientAmount`, are not visible in the outer function.
209209

210-
In short, each local scope can also see all the local scopes that
211-
contain it. The set of bindings visible inside a block is determined
212-
by the place of that block in the program text. Each local scope can
213-
also see all the local scopes that contain it, and all scopes can see
214-
the global scope. This approach to binding visibility is called
215-
_((lexical scoping))_.
210+
The set of bindings visible inside a block is determined by the place of
211+
that block in the program text. Each local scope can also see all the
212+
local scopes that contain it, and all scopes can see the global scope.
213+
This approach to binding visibility is called _((lexical scoping))_.
216214

217215
## Functions as values
218216

0 commit comments

Comments
 (0)