Struct LayoutCtx 

pub struct LayoutCtx<'a> {
    pub resolver: &'a dyn FontResolver,
    pub toc_headings: &'a [TocHeading],
    pub toc_heading_pages: Option<&'a HashMap<String, usize>>,
}

Fields

resolver: &'a dyn FontResolver

toc_headings: &'a [TocHeading]

Every heading (Text::outline_level) in the whole document, in document order — independent of pagination (issue #10’s TableOfContents), so identical in both layout passes.

toc_heading_pages: Option<&'a HashMap<String, usize>>

None during pass 1 (page numbers aren’t known yet — a TableOfContents renders its entries without one). Some during pass 2, keyed by each heading’s TocHeading::anchor, filled in from pass 1’s own result — the same “pass 1 informs pass 2” mechanism PageContext.total_pages uses for Header/Footer.

Implementations

impl<'a> LayoutCtx<'a>

pub fn new(resolver: &'a dyn FontResolver) -> Self

A LayoutCtx with no TableOfContents data — what every caller outside pagination::paginate wants (it fills in the real per-pass values itself).