Struct MultibufferExcerptSource 

pub struct MultibufferExcerptSource { /* private fields */ }

OA.23 — the ExcerptSourceResolver a multibuffer-aware host wires into the plugin host.

One handle, because a view answers the whole question: the registry maps a view to its excerpts (composed line → source buffer + line), and every source is an Arc<dyn Document> that carries its own path.

It first took a BufferStoreHandle too, on the reasoning that the registry could say which buffer and never which file. That was wrong, and wrong in the way that costs a whole slice: a scan view — the agenda — mints its sources with BufferId::next() and hands them to add_source, never to BufferStore::insert_document_buffer, because they are not buffers the user opened. So the store answered none for every agenda row, and the only tests were the two none paths, which pass either way. See a_scan_views_source_resolves_by_the_documents_own_path.

Lives here rather than in the plugin host because this crate owns the composed→source translation; the host cannot depend on it (layering), which is why the trait is abstract in lattice-core at all.

Implementations

impl MultibufferExcerptSource

pub fn new(views: MultibufferRegistryHandle) -> Self

Trait Implementations

impl Clone for MultibufferExcerptSource

fn clone(&self) -> MultibufferExcerptSource

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for MultibufferExcerptSource

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

Formats the value using the given formatter.

impl ExcerptSourceResolver for MultibufferExcerptSource

fn excerpt_source(&self, buffer: BufferId, line: u32) -> Option<ExcerptSource>

Where composed line of buffer came from.

fn source_line(&self, source: BufferId, line: u32) -> Option<String>

One line of a source document, without its trailing newline (slice OA.23b).