Struct DisplayBufferRequest 

pub struct DisplayBufferRequest {
    pub content: HelpContent,
    pub category: BufferDisplayCategory,
}

5.5.F.1: payload for RendererSignal::DisplayBuffer. Carries the lattice_help::HelpContent the host built + the category the renderer should dispatch it under. The renderer resolves the category to a lattice_core::ui::display::BufferDisplay (via its existing resolve_display) and routes through the matching surface. Why a struct instead of inline variant fields: keeps the RendererSignal variant size constant when more host-side do_* arms migrate over and want to attach side-channel data (e.g. a buffer-id token the renderer should mirror into its registry on completion); subsequent slices can add fields here without churning every RendererSignal match arm in every renderer.

Fields

content: HelpContent

The help-style content the renderer should surface. Built host-side from editor.* reads; never includes renderer- specific data.

category: BufferDisplayCategory

The category the renderer dispatches under. The renderer’s resolve_display(category) reads the per-category typed option (:set <category>.display = ...) to pick the concrete surface.

Trait Implementations

impl Clone for DisplayBufferRequest

fn clone(&self) -> DisplayBufferRequest

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for DisplayBufferRequest

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

Formats the value using the given formatter.