diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2016-11-10 10:24:14 -0800 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2016-11-10 10:24:14 -0800 |
| commit | f116818c7c6e98a5d9bfa7058096b42df85d8e1c (patch) | |
| tree | ba3458a0c51f67c27c7347b1c5f5be2fc33965e2 /057immutable.cc | |
| parent | b771d375d3e11dcf3e6e55175f2ae128448177a7 (diff) | |
| download | mu-f116818c7c6e98a5d9bfa7058096b42df85d8e1c.tar.gz | |
3656
Periodic cleanup to replace 'reply' with 'return' everywhere in the repo. I use 'reply' for students to help reinforce the metaphor of function calls as being like messages through a pipe. But that causes 'reply' to get into my muscle memory when writing Mu code for myself, and I worry that that makes Mu seem unnecessarily alien to anybody reading on Github. Perhaps I should just give it up? I'll try using 'return' with my next student.
Diffstat (limited to '057immutable.cc')
| -rw-r--r-- | 057immutable.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/057immutable.cc b/057immutable.cc index 53c7c171..7b4e331c 100644 --- a/057immutable.cc +++ b/057immutable.cc @@ -56,7 +56,7 @@ def foo p:&:d1 -> q:num [ load-ingredients x:&:d1 <- new d1:type *x <- put *x, p:offset, 34 # ignore this 'p' - reply 36 + return 36 ] container d1 [ p:num |