crossbeam-deque has no blocking pop: how do you use it?

[tomshackell]

I notice that crossbeam-deque doesn't appear to include a blocking pop. The find_task example returns an Option<T>. Is the intention that if you have a pool of threads they should all just spin-lock continuously polling for work, even when not in use? That seems extremely inefficient and it's really not clear how this is supposed to work practically. Maybe an example showing how you actually build a real multi-threaded task-scheduler using crossbeam-deque would help?

EDIT: Ah okay I see, this is just a very small piece of writing a practical work queue. All the hard stuff of getting the notifications right you have to do all that yourself.