about summary refs log tree commit diff stats
path: root/056shape_shifting_recipe.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 /056shape_shifting_recipe.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 '056shape_shifting_recipe.cc')
0 files changed, 0 insertions, 0 deletions
' href='#n123'>123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216