disruptor 4.3.0

//! Module with different strategies for waiting for an event to be published.
//!
//! The lowest latency possible is the [`BusySpin`] strategy.
//!
//! To "waste" less CPU time and power, use one of the other strategies which have higher latency.

use std::hint;
use std::thread;
use std::time::Duration;

use crate::Sequence;

/// Wait strategies are used by consumers when no new events are ready on the ring buffer.
pub trait WaitStrategy: Copy + Send {
	/// The wait strategy will wait for the sequence id being available.
	fn wait_for(&self, sequence: Sequence);
}

/// Busy spin wait strategy. Lowest possible latency.
#[derive(Copy, Clone)]
pub struct BusySpin;

impl WaitStrategy for BusySpin {
	#[inline]
	fn wait_for(&self, _sequence: Sequence) {
		// Do nothing, true busy spin.
	}
}

/// Busy spin wait strategy with spin loop hint which enables the processor to optimize its behavior
/// by e.g. saving power os switching hyper threads. Obviously, this can induce latency.
///
/// See also [`BusySpin`].
#[derive(Copy, Clone)]
pub struct BusySpinWithSpinLoopHint;

impl WaitStrategy for BusySpinWithSpinLoopHint {
	fn wait_for(&self, _sequence: Sequence) {
		hint::spin_loop();
	}
}

/// Sleeps for a specified amount of time.
///
/// Useful during development, or if you also want to use the Disruptor
/// for non latency critical parts of your application.
#[derive(Copy, Clone)]
pub struct Sleep {
	/// The amount of time to sleep.
	duration: Duration
}

impl Sleep {
	/// Create a `Sleep` wait strategy that sleeps the specified
	/// amount if no new events are ready for consumption.
	pub fn new(duration: Duration) -> Self {
		Self { duration }
	}
}

impl WaitStrategy for Sleep {
	fn wait_for(&self, _sequence: Sequence) {
		thread::sleep(self.duration);
	}
}