about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 1424 - the right way to make autogenerated_listsKartik K. Agaram2015-05-221-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 linesKartik K. Agaram2015-05-221-1/+34
|
* 1422 - page-based navigationKartik K. Agaram2015-05-221-3/+34
|
* 1421 - more snappy cursor movementKartik K. Agaram2015-05-221-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 movementKartik K. Agaram2015-05-221-0/+8
|
* 1419 - trace browser displays collapsed linesKartik K. Agaram2015-05-221-2/+16
|
* 1418 - starting trace-browser implementation in C++Kartik K. Agaram2015-05-222-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 tracesKartik K. Agaram2015-05-2113-43/+83
|
* 1416Kartik K. Agaram2015-05-213-27/+36
|
* 1415Kartik K. Agaram2015-05-211-25/+3
|
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-2123-325/+137
|
* 1413Kartik K. Agaram2015-05-212-67/+15
|
* 1412 - starting to clean up trace formatKartik K. Agaram2015-05-213-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.
* 1411Kartik K. Agaram2015-05-201-2/+5
|
* 1410Kartik K. Agaram2015-05-201-1/+2
|
* 1409Kartik K. Agaram2015-05-191-1/+1
|
* 1408Kartik K. Agaram2015-05-192-9/+9
|
* 1407Kartik K. Agaram2015-05-192-5/+5
|
* 1406Kartik K. Agaram2015-05-191-0/+5
|
* 1405Kartik K. Agaram2015-05-192-3/+9
|
* 1404 - undefined-behavior checks using clangKartik K. Agaram2015-05-182-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.)
* 1403Kartik K. Agaram2015-05-181-7/+6
|
* 1402Kartik K. Agaram2015-05-181-4/+6
|
* 1401 - shave 80% off chessboard test timeKartik K. Agaram2015-05-183-1/+15
| | | | It was all going to laboriously writing out 300+ MB to disk.
* 1400Kartik K. Agaram2015-05-181-5/+5
|
* 1399 - better 'unknown type' warningsKartik K. Agaram2015-05-185-14/+100
| | | | | | | | Implement warnings for types without definitions without constraining where type definitions must appear. We also eliminate the anti-pattern where a change in layer 10 had its test in layer 11 (commit 1383).
* 1398Kartik K. Agaram2015-05-181-2/+23
|
* 1397 - support unicode in screen checksKartik K. Agaram2015-05-182-31/+103
|
* 1396Kartik K. Agaram2015-05-171-16/+40
|
* 1395Kartik K. Agaram2015-05-171-3/+2
|
* 1394Kartik K. Agaram2015-05-171-2/+2
|
* 1393Kartik K. Agaram2015-05-171-0/+18
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-1737-331/+365
|
* 1390 - support non-integer literalsKartik K. Agaram2015-05-175-24/+60
| | | | | | | | | | | | | | | | | | | | Since '3.14159:literal' looks ugly, we'll just say '3.14159'. It's not like non-integers can be confused for anything but literals. Once I tried to turn reagent values into doubles, I uncovered a bug: arithmetic using signed integers is busted; if either operand of subtraction is unsigned the result is unsigned as well. If it needs to be negative: ka-boom. It was only masked because I was eventually storing the result in a long long int, where it was out of range, and so overflowing into the correct signed value. Once I switched to doubles the unsigned value would indeed fit without overflowing. Ka-boom. Yet another reminder that unsigned integers suck. I started using them mostly to avoid warnings in loops when comparing with .size(), which is usually a size_t. Who knows what other crap lurks here. Just use signed integers everywhere. (And avoid bitwise operators.)
* 1389Kartik K. Agaram2015-05-162-3/+3
|
* 1388Kartik K. Agaram2015-05-161-0/+1
|
* 1387Kartik K. Agaram2015-05-168-15/+15
|
* 1385Kartik K. Agaram2015-05-163-1/+4
|
* 1384Kartik K. Agaram2015-05-161-0/+6
|
* 1383 - warn on unknown typeKartik K. Agaram2015-05-165-2/+21
| | | | | | | | | | | | | This bit me in the last commit for the first time. Layer 010vm.cc is starting to look weird. It has references to stuff that gets implemented much later, like containers and exclusive containers. Its helpers are getting an increasing amount of logic. And it has no tests. I'm still inclined to think it's useful to have major data structures in one place, even if they aren't used for a bit. But those helpers should perhaps move out somehow or get some tests in the same layer.
* 1382 - implement continuationsKartik K. Agaram2015-05-161-0/+76
|
* 1381Kartik K. Agaram2015-05-151-1/+14
|
* 1380 - list data structureKartik K. Agaram2015-05-151-0/+55
|
* 1379 - avoid all uninitialized-memory issuesKartik K. Agaram2015-05-151-1/+13
|
* 1378Kartik K. Agaram2015-05-151-0/+1
|
* 1377 - handle github errorsKartik K. Agaram2015-05-141-1/+1
|
* 1376 - update github docsKartik K. Agaram2015-05-1448-1849/+3641
|
* 1375 - cleanupKartik K. Agaram2015-05-141-4/+3
|
* 1374 - chessboard end-to-end test passes!Kartik K. Agaram2015-05-145-19/+91
| | | | | | | | | | After like 40 seconds (because of the 120-column screen), but whatever. The final bug was that clear-screen wasn't actually working right for fake screens. (The trace is too large for github, so I'm going to leave it out for now.)
* 1373Kartik K. Agaram2015-05-141-1/+4
|