| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 1247 | Kartik K. Agaram | 2015-05-03 | 1 | -2/+2 |
| | | |||||
| * | 1246 | Kartik K. Agaram | 2015-05-03 | 1 | -4/+4 |
| | | |||||
| * | 1225 | Kartik K. Agaram | 2015-04-29 | 1 | -0/+4 |
| | | | | | Finally start tracing the actual instructions as they run. | ||||
| * | 1223 - more stable traces for parse scenarios | Kartik K. Agaram | 2015-04-29 | 1 | -4/+4 |
| | | |||||
| * | 1213 | Kartik K. Agaram | 2015-04-28 | 1 | -2/+2 |
| | | |||||
| * | 1194 | Kartik K. Agaram | 2015-04-24 | 1 | -0/+1 |
| | | |||||
| * | 1184 - finally, concurrency | Kartik K. Agaram | 2015-04-24 | 1 | -0/+1 |
| | | |||||
| * | 1166 | Kartik K. Agaram | 2015-04-24 | 1 | -2/+2 |
| | | | | | | | | 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. | ||||
| * | 1105 - more primitives for managing ingredients | Kartik K. Agaram | 2015-04-19 | 1 | -1/+1 |
| | | |||||
| * | 1084 | Kartik K. Agaram | 2015-04-17 | 1 | -2/+2 |
| | | |||||
| * | 1075 | Kartik K. Agaram | 2015-04-17 | 1 | -2/+2 |
| | | |||||
| * | 1074 | Kartik K. Agaram | 2015-04-17 | 1 | -2/+2 |
| | | |||||
| * | 1069 - rename record/field to container/element | Kartik K. Agaram | 2015-04-16 | 1 | -0/+29 |
| 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). | |||||