Skip to content

Commit c78b347

Browse files
committed
Update README
1 parent b2adf7d commit c78b347

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -751,7 +751,7 @@ for func in arr:
751751

752752
### Recursion
753753

754-
One call always access the current lambdex itself via `callee_` within a lambdex. The feature is quite handy since you don't need to assign a lambdex to a name for doing recursion.
754+
One can always access the current lambdex itself via `callee_` within a lambdex. The feature is quite handy since you don't need to assign a lambdex to a name for doing recursion.
755755

756756
```python
757757
# Summing from 1 to 10
@@ -1277,7 +1277,7 @@ The preference of "<" ">" over "<=" "=>" is that the previous ones consume only
12771277

12781278
The design is from two concerns.
12791279

1280-
1. A programmatic approaches may cause inconsistency at runtime, which is difficult for troubleshooting. For example, if one declares the aliasing in `mod/__init__.py` and uses the new keywords in `mod/A.py`, the aliasing works fine if `mod/A.py` imported as `mod.A`, but fails if run as a standalone script.
1280+
1. A programmatic approach may cause inconsistency at runtime, which is difficult for troubleshooting. For example, if one declares the aliasing in `mod/__init__.py` and uses the new keywords in `mod/A.py`, the aliasing works fine if `mod/A.py` imported as `mod.A`, but fails if run as a standalone script.
12811281
2. The compiler and formatter should behave consistently when processing the same file. If a programmatic approach used, the formatter must apply semantic analysis to figure out the aliasing rules, which is far more complicated.
12821282

12831283
---

0 commit comments

Comments
 (0)