about summary refs log tree commit diff stats
path: root/render.vim
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2014-11-08 10:31:37 -0800
committerKartik K. Agaram <vc@akkartik.com>2014-11-08 10:35:25 -0800
commitfc46ebddf0c802e3942d80446dcd6c8fc339c4fd (patch)
tree54cb92b6544dd71ed46a93f55f5f6951f99be509 /render.vim
parent3bec25ce266aef848fb2a87b9a9ee33ab80566b0 (diff)
downloadmu-fc46ebddf0c802e3942d80446dcd6c8fc339c4fd.tar.gz
263
I'm trying to think about how to write a test for the race condition,
and how to fix it. One thing that's been hard is even remembering where
it lies. It's not between wiping the watch and sleeping on it; that's
innocuous because the sleep would just immediately wake up. No, the race
condition lies between the empty check and the wipe.

For the innocuous race we could just create an atomic wipe-and-sleep.
But the more serious race requires a lock.

If we need a lock anyway, is there any reason to have two watch
variables?

I'm going to preserve these alternative functions in the code.
Alternatives will only ever be called from other alteratives or tests.
Diffstat (limited to 'render.vim')
0 files changed, 0 insertions, 0 deletions