| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 624 - no, that's all wrong, scratch 623 | Kartik K. Agaram | 2015-01-25 | 1 | -15/+15 |
| | | |||||
| * | 623 - 'nochange' to guard against race conditions | Kartik K. Agaram | 2015-01-25 | 1 | -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 again | Kartik K. Agaram | 2015-01-25 | 1 | -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. | ||||
| * | 618 | Kartik K. Agaram | 2015-01-25 | 1 | -0/+256 |