about summary refs log tree commit diff stats
path: root/003trace.test.cc
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2016-08-26 13:27:57 -0700
committerKartik K. Agaram <vc@akkartik.com>2016-08-26 13:27:57 -0700
commit029a3bdf53b523eded91a30177affdcace3bb2a1 (patch)
tree8984ca1073ee20950d74d091eca4fb07e04f321f /003trace.test.cc
parentad2604e893edbb3cde3d5e14cf4418acd3ef7d65 (diff)
downloadmu-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 '003trace.test.cc')
0 files changed, 0 insertions, 0 deletions
be74e5b2c04649e08b'>d1fc8866 ^
da077109 ^



d1fc8866 ^

1c1b6c31 ^

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139