Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 1450 | Kartik K. Agaram | 2015-05-24 | 1 | -1/+1 |
| | |||||
* | 1449 - use prompt/abort for delimited continuations | Kartik K. Agaram | 2015-05-24 | 1 | -44/+53 |
| | | | | This is *much* more nice-looking scenario. | ||||
* | 1448 | Kartik K. Agaram | 2015-05-24 | 1 | -0/+1 |
| | |||||
* | 1447 | Kartik K. Agaram | 2015-05-24 | 2 | -20/+55 |
| | |||||
* | 1446 - delimited continuations | Kartik K. Agaram | 2015-05-23 | 1 | -0/+145 |
| | | | | This is probably going to be embarrassing. | ||||
* | 1445 | Kartik K. Agaram | 2015-05-23 | 1 | -2/+1 |
| | |||||
* | 1444 | Kartik K. Agaram | 2015-05-23 | 3 | -5/+9 |
| | |||||
* | 1443 - bugfix in continuation support | Kartik K. Agaram | 2015-05-23 | 1 | -0/+6 |
| | | | | Thanks Anthony Di Franco (http://dfko.net) | ||||
* | 1442 | Kartik K. Agaram | 2015-05-23 | 1 | -1/+1 |
| | |||||
* | 1441 - give up on unit tests for 'random' | Kartik K. Agaram | 2015-05-23 | 1 | -1/+2 |
| | | | | | | | | | | I'd been hoping that I could simply pass in the previously-returned number to srand() to generate the next one in the series. But looks like rand() is more stateful than that. Another weirdness: I put in 'round' in the same layer because of the vague idea that it would help generate random integers. But that's all we get anyway. | ||||
* | 1440 | Kartik K. Agaram | 2015-05-23 | 1 | -0/+1 |
| | |||||
* | 1439 - support clang in addition to gcc | Kartik K. Agaram | 2015-05-23 | 3 | -3/+3 |
| | |||||
* | 1438 | Kartik K. Agaram | 2015-05-23 | 1 | -0/+42 |
| | |||||
* | 1437 | Kartik K. Agaram | 2015-05-23 | 1 | -1/+1 |
| | |||||
* | 1436 | Kartik K. Agaram | 2015-05-23 | 3 | -3/+8 |
| | |||||
* | 1435 | Kartik K. Agaram | 2015-05-23 | 1 | -3/+7 |
| | |||||
* | 1434 - support all unicode spaces | Kartik K. Agaram | 2015-05-23 | 7 | -21/+128 |
| | |||||
* | 1433 - 'trim' strings | Kartik K. Agaram | 2015-05-23 | 1 | -0/+96 |
| | |||||
* | 1432 - contrast scenarios and recipes | Kartik K. Agaram | 2015-05-23 | 1 | -2/+3 |
| | |||||
* | 1431 | Kartik K. Agaram | 2015-05-23 | 1 | -3/+3 |
| | |||||
* | 1430 | Kartik K. Agaram | 2015-05-22 | 1 | -1/+9 |
| | |||||
* | 1429 - third, possibly successful impl of collapse | Kartik K. Agaram | 2015-05-22 | 1 | -10/+5 |
| | |||||
* | 1428 - second attempt | Kartik K. Agaram | 2015-05-22 | 1 | -4/+1 |
| | | | | | This doesn't work either; some children are collapsed but not others (after the first expanded child). | ||||
* | 1427 - first attempt at collapsing lines | Kartik K. Agaram | 2015-05-22 | 1 | -0/+27 |
| | | | | | | Collapsing is harder than expanding. This approach doesn't work because I end up sometimes with visible lines whose parents aren't visible anymore. | ||||
* | 1426 | Kartik K. Agaram | 2015-05-22 | 1 | -4/+0 |
| | | | | | | As often happens, the asserts I come up with fail to survive contact with reality. In this case because the current line may not have anything left to expand. | ||||
* | 1425 | Kartik K. Agaram | 2015-05-22 | 1 | -0/+1 |
| | |||||
* | 1424 - the right way to make autogenerated_lists | Kartik K. Agaram | 2015-05-22 | 1 | -1/+2 |
| | | | | | Ever since 1403 mu depended on a phony target and so was always considered stale. This commit improves on that fix. | ||||
* | 1423 - expand lines | Kartik K. Agaram | 2015-05-22 | 1 | -1/+34 |
| | |||||
* | 1422 - page-based navigation | Kartik K. Agaram | 2015-05-22 | 1 | -3/+34 |
| | |||||
* | 1421 - more snappy cursor movement | Kartik K. Agaram | 2015-05-22 | 1 | -4/+16 |
| | | | | | Persist the mapping from screen row to trace index between refreshes. Now we have to remember to refresh the mapping anytime we change state. | ||||
* | 1420 - first steps in cursor movement | Kartik K. Agaram | 2015-05-22 | 1 | -0/+8 |
| | |||||
* | 1419 - trace browser displays collapsed lines | Kartik K. Agaram | 2015-05-22 | 1 | -2/+16 |
| | |||||
* | 1418 - starting trace-browser implementation in C++ | Kartik K. Agaram | 2015-05-22 | 2 | -1/+69 |
| | | | | | | | | | I still have no idea how it will hook up to the rest. Parsing traces will be slow. I can't test it like this. Writing the large trace data structure to mu memory will be slow. But let's at least see the new algorithm in action. (Not in this commit; so far we just render the first n lines from the chessboard trace, and wait for a 'q' or 'Q' to quit.) | ||||
* | 1417 - draft zoom levels in traces | Kartik K. Agaram | 2015-05-21 | 13 | -43/+83 |
| | |||||
* | 1416 | Kartik K. Agaram | 2015-05-21 | 3 | -27/+36 |
| | |||||
* | 1415 | Kartik K. Agaram | 2015-05-21 | 1 | -25/+3 |
| | |||||
* | 1414 - traces now robust to new recipes/types | Kartik K. Agaram | 2015-05-21 | 23 | -325/+137 |
| | |||||
* | 1413 | Kartik K. Agaram | 2015-05-21 | 2 | -67/+15 |
| | |||||
* | 1412 - starting to clean up trace format | Kartik K. Agaram | 2015-05-21 | 3 | -193/+28 |
| | | | | | Many features of my trace layer were just inherited blindly from wart but lying unused in this project. Throw them out while we're at it. | ||||
* | 1411 | Kartik K. Agaram | 2015-05-20 | 1 | -2/+5 |
| | |||||
* | 1410 | Kartik K. Agaram | 2015-05-20 | 1 | -1/+2 |
| | |||||
* | 1409 | Kartik K. Agaram | 2015-05-19 | 1 | -1/+1 |
| | |||||
* | 1408 | Kartik K. Agaram | 2015-05-19 | 2 | -9/+9 |
| | |||||
* | 1407 | Kartik K. Agaram | 2015-05-19 | 2 | -5/+5 |
| | |||||
* | 1406 | Kartik K. Agaram | 2015-05-19 | 1 | -0/+5 |
| | |||||
* | 1405 | Kartik K. Agaram | 2015-05-19 | 2 | -3/+9 |
| | |||||
* | 1404 - undefined-behavior checks using clang | Kartik K. Agaram | 2015-05-18 | 2 | -2/+10 |
| | | | | | | | | While I'm at it I also explored turning on optimization. With optimization compile+test of the chessboard app takes 10+3s, while without optimization it takes 3+8s. So we're still better off without optimizations in a tight debug loop. (Since we stopped tracing the big chessboard test.) | ||||
* | 1403 | Kartik K. Agaram | 2015-05-18 | 1 | -7/+6 |
| | |||||
* | 1402 | Kartik K. Agaram | 2015-05-18 | 1 | -4/+6 |
| | |||||
* | 1401 - shave 80% off chessboard test time | Kartik K. Agaram | 2015-05-18 | 3 | -1/+15 |
| | | | | It was all going to laboriously writing out 300+ MB to disk. |