Struct DecorationEpoch 

pub struct DecorationEpoch(/* private fields */);

The counter a guest bumps to say “my decorations changed, though the document did not” (OA.30).

The hole this fills

maybe_refresh_wasm_decorations re-runs producers on exactly two triggers: the producer registry changed, or this buffer’s cached document_version moved. Both are about things the HOST can see. A producer whose output depends on its own view-local state — the agenda’s bulk marks are the case that found this — changes neither, so its first answer is cached forever and every later toggle paints nothing.

That is the same shape refresh-view (OA.15a) closed one level up: a guest could compute a new answer and had no way to say so. This is the gutter’s version of it.

Why a bare counter, and not a per-buffer map

The refresh pump only ever refetches the ACTIVE buffer, so a bump means “the next tick should refetch” and nothing finer would be read. A per-buffer key would be a more precise answer to a question nobody asks, and the cost of being coarse is one extra producer call — off the actor thread, on a tick, for a buffer that is on screen anyway.

Implementations

impl DecorationEpoch

pub fn bump(&self)

Say that a producer’s answer has changed. Cheap enough to call per keystroke: one relaxed increment.

pub fn get(&self) -> u64

The current value, for the refresh gate to compare against its last.

Trait Implementations

impl Debug for DecorationEpoch

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

Formats the value using the given formatter.

impl Default for DecorationEpoch

fn default() -> DecorationEpoch

Returns the “default value” for a type.