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 /sandbox/007-sandbox-delete.mu | |
| 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 'sandbox/007-sandbox-delete.mu')
| -rw-r--r-- | sandbox/007-sandbox-delete.mu | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sandbox/007-sandbox-delete.mu b/sandbox/007-sandbox-delete.mu index 9577a3b3..576d6761 100644 --- a/sandbox/007-sandbox-delete.mu +++ b/sandbox/007-sandbox-delete.mu @@ -81,7 +81,7 @@ def should-attempt-delete? click-row:num, click-column:num, env:&:environment -> load-ingredients # are we below the sandbox editor? click-sandbox-area?:bool <- click-on-sandbox-area? click-row, env - reply-unless click-sandbox-area?, 0/false + return-unless click-sandbox-area?, 0/false # narrower, is the click in the columns spanning the 'copy' button? first-sandbox:&:editor <- get *env, current-sandbox:offset assert first-sandbox, [!!] |