For users outside of RTOS such as bevy, spinning with exponential back-off is a good enough solution to avoid the issue raised in #583.
We could add an additional type parameter to Queue, which implements or not some form of backoff, similar to crossbeam-utils' Backoff, or does nothing.
This would allow having the option for downstreams who need it, without incurring any cost for downstreams who don't.
For users outside of RTOS such as bevy, spinning with exponential back-off is a good enough solution to avoid the issue raised in #583.
We could add an additional type parameter to
Queue, which implements or not some form of backoff, similar to crossbeam-utils'Backoff, or does nothing.This would allow having the option for downstreams who need it, without incurring any cost for downstreams who don't.