This is a very real problem with cvars on normal systems, and all of channels will not work if spurious wakeups are accepted. This problem is just solved with a synchronized flag (accessed in the cvar's lock) to see whether a signal() actually happened or whether it's spurious. |
||
|---|---|---|
| .. | ||
| io | ||
| lib.rs | ||
| task.rs | ||