Struct Markers 

pub struct Markers<E> {
    pub failure_marker: bool,
    pub retriable: Box<dyn Fn(&E) -> bool + Sync + Send>,
    pub success_marker: bool,
    pub hashes: bool,
    pub folder: bool,
}

Fields

failure_marker: bool

Use failure markers {output}.failure to skip previously failed calls.

retriable: Box<dyn Fn(&E) -> bool + Sync + Send>

success_marker: bool

Use success markers {output}.success to rerun when arguments or code have changed. This only makes sense with the hashes flag.

hashes: bool

Use code and arguments hashes for markers. If they changed, rerun failed and successful runs.

folder: bool

Assume the output attribute is a folder and store the markers in {output}/success and {output}/failure.

Implementations

impl<E> Markers<E>

pub fn folder(self) -> Self

pub fn retriable( self, retriable: impl Fn(&E) -> bool + Sync + Send + 'static, ) -> Self

Trait Implementations

impl<E> Default for Markers<E>

fn default() -> Self

Returns the “default value” for a type.

impl<T, E> Strategy<Result<T, E>> for Markers<E>

type E = Error

fn skip(&self, output: &Path, args_hash: u64, code_hash: u64) -> bool

Should we skip generating the output? This can take into account the hash of the arguments and the code, provided as arguments.

fn callback( &self, result: &Result<T, E>, output: &Path, args_hash: u64, code_hash: u64, ) -> Result<(), Error>

When the output is not skipped, this is called after processing, right before returning.