about summary refs log tree commit diff stats
path: root/cpp/.traces/reply_container
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-04-24 17:09:17 -0700
committerKartik K. Agaram <vc@akkartik.com>2015-04-24 17:09:17 -0700
commit2fb94e3c4c4ade042fc1944f1bfa64609bff40b4 (patch)
treea3b649a53a0b634d3110daf2f8357d372a560841 /cpp/.traces/reply_container
parent544a1f1e17d909673f08a50b97fc9d00df431eb4 (diff)
downloadmu-2fb94e3c4c4ade042fc1944f1bfa64609bff40b4.tar.gz
1166
Why did I think STL's map wasn't efficient? It has logarithmic
complexity (maintains a tree internally) and is faster than hashing for
small containers. It's the more portable solution and should be what I
turn to by default.
Diffstat (limited to 'cpp/.traces/reply_container')
-rw-r--r--cpp/.traces/reply_container4
1 files changed, 2 insertions, 2 deletions
diff --git a/cpp/.traces/reply_container b/cpp/.traces/reply_container
index 9a5d430f..10cc9548 100644
--- a/cpp/.traces/reply_container
+++ b/cpp/.traces/reply_container
@@ -8,12 +8,12 @@ parse/0:   ingredient: {name: "35", value: 0, type: 0, properties: ["35": "liter
 parse/0:   product: {name: "13", value: 0, type: 1, properties: ["13": "integer"]}
 parse/0: instruction: 28
 parse/0:   ingredient: {name: "12", value: 0, type: 6, properties: ["12": "point"]}
+after-brace/0: recipe main
+after-brace/0: f ...
 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