diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2016-08-26 13:27:57 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2016-08-26 13:27:57 -0700 |
commit | 029a3bdf53b523eded91a30177affdcace3bb2a1 (patch) | |
tree | 8984ca1073ee20950d74d091eca4fb07e04f321f /nqueens.mu | |
parent | ad2604e893edbb3cde3d5e14cf4418acd3ef7d65 (diff) | |
download | mu-029a3bdf53b523eded91a30177affdcace3bb2a1.tar.gz |
3258
In the process of debugging the last couple of commits (though I no longer remember exactly how) I noticed that 'wait-for-routine' only waits until the target routine stops running for any reason, including when it blocks on something. That's not the synchronization primitive we want in production code, even if it's necessary for some scenarios like 'buffer-lines-blocks-until-newline'. So we rename the old 'wait-for-routine' primitive to 'wait-for-routine-to-block', and create a new version of 'wait-for-routine' that say callers of 'start-writing' can safely use, because it waits until a target routine actually completes (either successfully or not).
Diffstat (limited to 'nqueens.mu')
0 files changed, 0 insertions, 0 deletions