diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2016-03-08 01:30:14 -0800 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2016-03-08 01:46:47 -0800 |
| commit | 1ead356219bb2eb59487d1012f837bd07ec336f5 (patch) | |
| tree | af15f390b81e4d6b3e0940c5756a0d7fd1060bb5 /static_dispatch.mu | |
| parent | 27ba0937a3747684f299bb7a8b3cdd0fbb689db3 (diff) | |
| download | mu-1ead356219bb2eb59487d1012f837bd07ec336f5.tar.gz | |
2735 - define recipes using 'def'
I'm dropping all mention of 'recipe' terminology from the Readme. That way I hope to avoid further bike-shedding discussions while I very slowly decide on the right terminology with my students. I could be smarter in my error messages and use 'recipe' when code uses it and 'function' otherwise. But what about other words like ingredient? It would all add complexity that I'm not yet sure is worthwhile. But I do want separate experiences for veteran programmers reading about Mu on github and for people learning programming using Mu.
Diffstat (limited to 'static_dispatch.mu')
| -rw-r--r-- | static_dispatch.mu | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/static_dispatch.mu b/static_dispatch.mu index 00160a2a..9ef3e33c 100644 --- a/static_dispatch.mu +++ b/static_dispatch.mu @@ -1,16 +1,16 @@ -recipe test a:number -> b:number [ +def test a:number -> b:number [ local-scope load-ingredients b <- add a, 1 ] -recipe test a:number, b:number -> c:number [ +def test a:number, b:number -> c:number [ local-scope load-ingredients c <- add a, b ] -recipe main [ +def main [ local-scope a:number <- test 3 # selects single-ingredient version $print a, 10/newline |