It's late and I must be missing something (or maybe a lot).
ordered by key? ordered by value? ordered by insertion/update time?
Ordered for enumeration? or ordered where I can provide my own search? binary search is great, but I can think cases with better performance lookups with a bias in one direction.<p>I guess there are two main things.
1. what does ordered mean? I can think of lots of cases where having access to order would be super helpful. How do I tag the thing(s) I care about for lookup>
2. I'm not a super fan of go, but randomizing enumeration of maps was a really good move for avoiding inadvertent dependence on order.<p>I checked again, and I still don't see what order "means" (safari on OS X. maybe it's not rendering right?)<p>_edit_<p>after digging a little deeper, I guess I want to add 3
How are ties broken? Fastest result? Highest memory address?<p>Ordered KV would be super handy. But the devil is in the details, and I can't find any details.