Struct ReloadEvent 

#[non_exhaustive]
pub struct ReloadEvent<T> {
    pub previous: Option<Arc<T>>,
    pub current: Arc<T>,
    pub reason: ReloadReason,
    pub meta: SnapshotMeta,
}

One install, as an event.

What on_reload_with hands a hook, and what the two-argument on_reload cannot say: why the snapshot moved, which generation it became, and — through previous — that there was nothing before it.

The first install is an event with previous: None. The pair form has nowhere to put that and so does not fire for it at all; this form does, which is what makes ReloadReason::Initial reachable from a hook.

A note on Debug

It prints the reason, the metadata and whether there was a previous snapshot — never the snapshots themselves, however T renders. An event is a diagnostic, a {:?} of one lands in a log, and a configuration holds passwords. Reach for the current field when you want the values; that is a deliberate second step.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

previous: Option<Arc<T>>

The snapshot that was serving until now, or None when this install is the first — there was no configuration before it.

current: Arc<T>

The snapshot now serving.

reason: ReloadReason

What caused this install.

meta: SnapshotMeta

The generation this install became, and when it landed.

Trait Implementations

impl<T> Clone for ReloadEvent<T>

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl<T> Debug for ReloadEvent<T>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.