about summary refs log tree commit diff stats
path: root/chessboard.arc.t
Commit message (Collapse)AuthorAgeFilesLines
* 856 - stop perturbing traces on new functionsKartik K. Agaram2015-03-011-138/+112
| | | | | Still hacky, but now we can standardize the couple of different workflows we need.
* 750Kartik K. Agaram2015-02-151-2/+2
|
* 742 - turns out chessboard test logs were incompleteKartik K. Agaram2015-02-111-1/+3
| | | | | Now that we aren't loading system software for every test we can afford to log the loading of test functions.
* 729Kartik K. Agaram2015-02-101-8/+8
|
* 718 - disable raw memory warnings in testsKartik K. Agaram2015-02-081-0/+1
|
* 624 - no, that's all wrong, scratch 623Kartik K. Agaram2015-01-251-15/+15
|
* 623 - 'nochange' to guard against race conditionsKartik K. Agaram2015-01-251-15/+15
| | | | | | | | | I dunno, this may all be a wild goose chase. I haven't been disciplined in tagging in-out arguments in 'read-move' and its helpers. Maybe I should just drop those 'nochange' oargs in 'read' and 'write'. Maybe I should reserve output args only for return values that callers might actually care about, and use more conventional metadata like 'const' or 'unique' or 'inout' on other args.
* 620 - fix broken examples and tests againKartik K. Agaram2015-01-251-8/+14
| | | | | | | | | I just did this in 611; what's the point of all this if tests can't stay passing? I don't understand why buffered-stdin.mu needs to preempt itself. stdin and buffered-stdin somehow end up sharing a single circular buffer, that's probably causing a race condition.
* 618Kartik K. Agaram2015-01-251-0/+256