Struct tokio::runtime::blocking::schedule::BlockingSchedule

pub(crate) struct BlockingSchedule {
    hooks: TaskHarnessScheduleHooks,
}

task::Schedule implementation that does nothing (except some bookkeeping in test-util builds). This is unique to the blocking scheduler as tasks scheduled are not really futures but blocking operations.

We avoid storing the task by forgetting it in bind and re-materializing it in release.

Fields

hooks: TaskHarnessScheduleHooks

Implementations

impl BlockingSchedule

pub(crate) fn new(handle: &Handle) -> Self

Trait Implementations

impl Schedule for BlockingSchedule

fn release(&self, _task: &Task<Self>) -> Option<Task<Self>>

The task has completed work and is ready to be released. The scheduler should release it immediately and return it. The task module will batch the ref-dec with setting other options.

fn schedule(&self, _task: Notified<Self>)

Schedule the task

fn hooks(&self) -> TaskHarnessScheduleHooks

fn yield_now(&self, task: Notified<Self>)

Schedule the task to run in the near future, yielding the thread to other tasks.

fn unhandled_panic(&self)

Polling the task resulted in a panic. Should the runtime shutdown?