Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 1116 - simpler memory checks | Kartik K. Agaram | 2015-04-20 | 1 | -0/+29 |
| | |||||
* | 1109 - interpolate strings | Kartik K. Agaram | 2015-04-20 | 3 | -0/+2078 |
| | |||||
* | 1108 - check for typos in memory expectations in scenarios | Kartik K. Agaram | 2015-04-20 | 1 | -0/+5 |
| | |||||
* | 1107 | Kartik K. Agaram | 2015-04-20 | 1 | -0/+3 |
| | |||||
* | 1105 - more primitives for managing ingredients | Kartik K. Agaram | 2015-04-19 | 32 | -50/+99 |
| | |||||
* | 1103 | Kartik K. Agaram | 2015-04-19 | 1 | -0/+11 |
| | |||||
* | 1101 | Kartik K. Agaram | 2015-04-19 | 13 | -22/+22 |
| | |||||
* | 1100 | Kartik K. Agaram | 2015-04-19 | 1 | -0/+759 |
| | |||||
* | 1099 - new recipe: convert integer to decimal string | Kartik K. Agaram | 2015-04-18 | 7 | -4/+1189 |
| | |||||
* | 1097 - 'grow-buffer' works the first time! | Kartik K. Agaram | 2015-04-18 | 1 | -0/+355 |
| | | | | | | | | | | | | | | | | | | | I thought I'd need to duplicate scenarios to simulate running some code, making some checks, running some more code. But I can just keep saving state to raw locations! I'd still have to manage raw locations myself, though. And it can be ping-pongy to have to check on the other blocks then go back to the run block. But what's the alternative? Multiple run blocks (even excluding the implementation effort) raise questions of namespace sharing across them. If it gets too bad I can intersperse recipes inside the scenario. Yes, that will work. Of course, overly long tests might themselves be a bad idea. We'll see, this is all terra incognita syntactically speaking. This might not be enough to check that a routine is waiting on a channel, but should keep us until then. Wait, even there what you need is a way to check on the status of your child routines. Yeah, doable. Even if we're getting ahead of ourselves. | ||||
* | 1090 | Kartik K. Agaram | 2015-04-17 | 4 | -11/+537 |
| | |||||
* | 1089 | Kartik K. Agaram | 2015-04-17 | 1 | -0/+51 |
| | |||||
* | 1088 - start porting the 'buffer' type | Kartik K. Agaram | 2015-04-17 | 1 | -0/+204 |
| | |||||
* | 1087 - mu files can now define containers and exclusive containers | Kartik K. Agaram | 2015-04-17 | 2 | -0/+10 |
| | |||||
* | 1086 - support variant names in 'maybe-convert' | Kartik K. Agaram | 2015-04-17 | 1 | -0/+32 |
| | |||||
* | 1085 - to access variants of sum types use 'maybe-convert' | Kartik K. Agaram | 2015-04-17 | 2 | -0/+62 |
| | |||||
* | 1084 | Kartik K. Agaram | 2015-04-17 | 29 | -51/+51 |
| | |||||
* | 1083 - start of a sum type for mu | Kartik K. Agaram | 2015-04-17 | 1 | -0/+34 |
| | |||||
* | 1075 | Kartik K. Agaram | 2015-04-17 | 43 | -145/+130 |
| | |||||
* | 1074 | Kartik K. Agaram | 2015-04-17 | 30 | -52/+52 |
| | |||||
* | 1069 - rename record/field to container/element | Kartik K. Agaram | 2015-04-16 | 5 | -2/+2 |
| | | | | | | | | | 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). | ||||
* | 1066 - bugfix: support string literals with colons | Kartik K. Agaram | 2015-04-15 | 1 | -0/+8 |
| | |||||
* | 1063 - variable names for surrounding spaces now work | Kartik K. Agaram | 2015-04-14 | 10 | -1/+137 |
| | | | | This was a pain to debug. | ||||
* | 1061 | Kartik K. Agaram | 2015-04-14 | 1 | -0/+14 |
| | |||||
* | 1058 - scenarios can now check trace | Kartik K. Agaram | 2015-04-12 | 3 | -0/+29 |
| | |||||
* | 1054 | Kartik K. Agaram | 2015-04-12 | 1 | -0/+11 |
| | |||||
* | 1050 | Kartik K. Agaram | 2015-04-11 | 5 | -108/+124 |
| | |||||
* | 1046 - mu programs can now add to the trace | Kartik K. Agaram | 2015-04-09 | 1 | -0/+7 |
| | | | | Still just raw strings, but interpolation is coming. | ||||
* | 1045 | Kartik K. Agaram | 2015-04-09 | 23 | -38/+38 |
| | |||||
* | 1042 - start saving traces in mu scenarios | Kartik K. Agaram | 2015-04-08 | 5 | -0/+791 |
| | |||||
* | 1030 - better test isolation for break/loop | Kartik K. Agaram | 2015-04-07 | 20 | -26/+26 |
| | | | | | | | I've been resetting all recipes after every single test, but the arc version has shown that this gets slow all too quickly. And the longer I wait to fix it the harder it gets to fix. Already, boy, were this and the next couple of commits hard to track down. | ||||
* | 1017 | Kartik K. Agaram | 2015-04-04 | 1 | -0/+11 |
| | |||||
* | 1013 | Kartik K. Agaram | 2015-04-03 | 21 | -35/+35 |
| | |||||
* | 1010 | Kartik K. Agaram | 2015-04-03 | 5 | -7/+57 |
| | |||||
* | 1009 | Kartik K. Agaram | 2015-04-03 | 1 | -0/+37 |
| | |||||
* | 1007 | Kartik K. Agaram | 2015-04-03 | 5 | -8/+5 |
| | |||||
* | 1002 | Kartik K. Agaram | 2015-04-02 | 1 | -0/+1 |
| | |||||
* | 1001 | Kartik K. Agaram | 2015-04-02 | 1 | -0/+35 |
| | |||||
* | 1000 | Kartik K. Agaram | 2015-03-31 | 2 | -2/+31 |
| | |||||
* | 999 | Kartik K. Agaram | 2015-03-31 | 2 | -2/+9 |
| | |||||
* | 998 - convenient string initialization | Kartik K. Agaram | 2015-03-30 | 2 | -1/+23 |
| | |||||
* | 997 | Kartik K. Agaram | 2015-03-30 | 89 | -497/+497 |
| | |||||
* | 996 - string literals | Kartik K. Agaram | 2015-03-30 | 3 | -2/+11 |
| | |||||
* | 994 - spaces now check bounds | Kartik K. Agaram | 2015-03-29 | 2 | -4/+25 |
| | | | | I'm not testing for bounds-check errors yet, though. | ||||
* | 992 - c++ chain spaces for lexical scope | Kartik K. Agaram | 2015-03-28 | 1 | -0/+29 |
| | |||||
* | 991 | Kartik K. Agaram | 2015-03-28 | 1 | -3/+3 |
| | |||||
* | 990 | Kartik K. Agaram | 2015-03-28 | 1 | -0/+28 |
| | |||||
* | 989 | Kartik K. Agaram | 2015-03-28 | 1 | -0/+50 |
| | |||||
* | 987 - c++: memory allocator | Kartik K. Agaram | 2015-03-27 | 1 | -0/+27 |
| | |||||
* | 986 | Kartik K. Agaram | 2015-03-27 | 17 | -42/+42 |
| |