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.

1 files changed, 1 insertions, 1 deletions

diff --git a/034address.cc b/034address.cc
index 5d453684..63a6cbdf 100644
--- a/034address.cc
+++ b/034address.cc
@@ -5,7 +5,7 @@
 //: units (containers or arrays) that may contain many different primitives at
 //: once. Containers and arrays can grow quite large in complex programs, and
 //: we'd like some way to efficiently share them between recipes without
-//: constantly having to make copies. Right now 'next-ingredient' and 'reply'
+//: constantly having to make copies. Right now 'next-ingredient' and 'return'
 //: copy data across recipe boundaries. To avoid copying large quantities of
 //: data around, we'll use *addresses*. An address is a bookmark to some
 //: arbitrary quantity of data (the *payload*). It's a primitive, so it's as