diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-04-16 10:35:49 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-04-16 10:35:49 -0700 |
commit | db5c9550e972d114aaabb95b14cfd1e3ea185349 (patch) | |
tree | 9217134d1154e45f5375f94c9b5788530fbf8cb7 /cpp/.traces/reply_record | |
parent | d6852155e5308e2bb347402bf9e069c7153c2319 (diff) | |
download | mu-db5c9550e972d114aaabb95b14cfd1e3ea185349.tar.gz |
1069 - rename record/field to container/element
This seems more obvious to laypeople. I've also come up with a design for sum types: I'm going to call them exclusive containers. You call 'get' on containers, 'index' on arrays, and 'maybe-convert' on exclusive containers (as well as tagged types, but that's even later).
Diffstat (limited to 'cpp/.traces/reply_record')
-rw-r--r-- | cpp/.traces/reply_record | 29 |
1 files changed, 0 insertions, 29 deletions
diff --git a/cpp/.traces/reply_record b/cpp/.traces/reply_record deleted file mode 100644 index 1a3541e6..00000000 --- a/cpp/.traces/reply_record +++ /dev/null @@ -1,29 +0,0 @@ -parse/0: instruction: 1001 -parse/0: ingredient: {name: "2", value: 0, type: 0, properties: ["2": "literal"]} -parse/0: product: {name: "3", value: 0, type: 6, properties: ["3": "point"]} -parse/0: instruction: 22 -parse/0: product: {name: "12", value: 0, type: 1, properties: ["12": "integer"]} -parse/0: instruction: 1 -parse/0: ingredient: {name: "35", value: 0, type: 0, properties: ["35": "literal"]} -parse/0: product: {name: "13", value: 0, type: 1, properties: ["13": "integer"]} -parse/0: instruction: 23 -parse/0: ingredient: {name: "12", value: 0, type: 6, properties: ["12": "point"]} -after-brace/0: recipe f -after-brace/0: next-ingredient ... -after-brace/0: copy ... -after-brace/0: reply ... -after-brace/0: recipe main -after-brace/0: f ... -run/0: instruction main/0 -run/0: instruction f/0 -run/0: product 0 is 2 -mem/0: storing 2 in location 12 -run/0: instruction f/1 -run/0: ingredient 0 is 35 -mem/0: storing 35 in location 13 -run/0: instruction f/2 -mem/0: location 12 is 2 -mem/0: location 13 is 35 -run/0: result 0 is [2, 35] -mem/0: storing 2 in location 3 -mem/0: storing 35 in location 4 |