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 /055shape_shifting_container.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 '055shape_shifting_container.cc')
| -rw-r--r-- | 055shape_shifting_container.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/055shape_shifting_container.cc b/055shape_shifting_container.cc index dec225dc..1953a3c6 100644 --- a/055shape_shifting_container.cc +++ b/055shape_shifting_container.cc @@ -244,7 +244,7 @@ def main [ +run: {6: ("foo" "point")} <- merge {1: "literal", "y": ()}, {23: "literal"} +mem: storing 1 in location 6 +mem: storing 23 in location 7 -+run: reply ++run: return # no other stores % CHECK_EQ(trace_count_prefix("mem", "storing"), 7); |