about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 902: c++: calling recipes with ingredientsKartik K. Agaram2015-03-144-8/+62
|
* 901Kartik K. Agaram2015-03-137-1/+24
|
* 900 - c++: calling 'recipes'Kartik K. Agaram2015-03-134-8/+53
|
* 899 - undo 898Kartik K. Agaram2015-03-131-11/+4
|
* 898 - experiment: make memory a vectorKartik K. Agaram2015-03-131-3/+11
| | | | | | | But racket takes too long to allocate a million locations, and anything smaller is currently infeasible. Ok, forget how slow writing to memory is, and focus on the C++ version.
* 897 - trying to save a short chessboard logKartik K. Agaram2015-03-131-6/+21
| | | | But it looks like it will take 1500 minutes at 100% CPU!
* 896 - c++: routineKartik K. Agaram2015-03-121-11/+20
|
* 895Kartik K. Agaram2015-03-122-1/+37
|
* 894Kartik K. Agaram2015-03-121-0/+2
|
* 893 - trying to take traces of chessboard appKartik K. Agaram2015-03-122-1/+7
|
* 892 - warning for bugs like 887Kartik K. Agaram2015-03-121-0/+25
|
* 890Kartik K. Agaram2015-03-122-1/+2
|
* 889 - ah, fixed that final errorKartik K. Agaram2015-03-122-0/+36
|
* 888Kartik K. Agaram2015-03-121-20/+0
|
* 887 - first pass of pagination bugs squashedKartik K. Agaram2015-03-112-53/+127
| | | | | | | | This must be the second or third time I've mis-tagged a literal as 'integer'.. I also spotted an error with the cursor bouncing out above the screen area of the trace browser. But I haven't been able to recreate it..
* 886Kartik K. Agaram2015-03-113-21/+71
| | | | Another test, but now the tests run 50% slower (8 vs 12 minutes)
* 885Kartik K. Agaram2015-03-112-1/+2
|
* 884 - expand/collapse now seems page-awareKartik K. Agaram2015-03-112-36/+185
|
* 883Kartik K. Agaram2015-03-112-27/+21
|
* 882Kartik K. Agaram2015-03-103-21/+70
|
* 881Kartik K. Agaram2015-03-103-0/+3
|
* 880 - new personal convention: capitalize names in proseKartik K. Agaram2015-03-101-12/+12
|
* 879 - debug prints shouldn't mess up interactive runsKartik K. Agaram2015-03-092-14/+19
|
* 878Kartik K. Agaram2015-03-091-156/+156
|
* 877 - supporting pages in expandKartik K. Agaram2015-03-092-14/+79
|
* 876Kartik K. Agaram2015-03-091-0/+2
|
* 875Kartik K. Agaram2015-03-092-7/+27
|
* 874Kartik K. Agaram2015-03-091-3/+3
|
* 873Kartik K. Agaram2015-03-091-15/+0
|
* 872Kartik K. Agaram2015-03-091-1/+1
|
* 871Kartik K. Agaram2015-03-081-8/+8
|
* 870 - page-up starting to look solidKartik K. Agaram2015-03-081-0/+70
|
* 869Kartik K. Agaram2015-03-073-43/+333
| | | | | | | The repeated need for bugfixes after every new test isn't very confidence-inducing. On the other hand, I'm starting to get into a cadence where fixes have been easy to make. We'll see. Monotonic progress continues.
* 868Kartik K. Agaram2015-03-071-8/+0
|
* 867Kartik K. Agaram2015-03-061-0/+16
|
* 866 - starting to finally gain confidence in page-upKartik K. Agaram2015-03-062-105/+140
|
* 865Kartik K. Agaram2015-03-061-3/+7
|
* 864Kartik K. Agaram2015-03-062-28/+80
|
* 863Kartik K. Agaram2015-03-061-1/+0
|
* 862Kartik K. Agaram2015-03-061-0/+24
|
* 861Kartik K. Agaram2015-03-051-5/+10
|
* 860Kartik K. Agaram2015-03-042-4/+38
| | | | A new intermediate test might help.
* 859Kartik K. Agaram2015-03-022-54/+238
| | | | | | Intermediate snapshot after 2 days of desultorily debugging this still-failing test. Our divising of the problem into cases just seems wrong right now.
* 858Kartik K. Agaram2015-03-011-2/+1
| | | | | Don't warn when reusing function names in tests, instead just dump section titles in the trace to aid navigation.
* 857Kartik K. Agaram2015-03-011-23/+23
|
* 856 - stop perturbing traces on new functionsKartik K. Agaram2015-03-013-290/+267
| | | | | Still hacky, but now we can standardize the couple of different workflows we need.
* 855 - page-up fleshed out, but needs a lot more testsKartik K. Agaram2015-03-012-2/+134
|
* 854Kartik K. Agaram2015-03-011-1/+3
|
* 853Kartik K. Agaram2015-02-281-6/+19
|
* 852 - page-down stitches expanded lines properlyKartik K. Agaram2015-02-283-10/+143
|