#[non_exhaustive]pub struct NodePlan {
pub shape: TileShape,
pub materialize: bool,
pub cacheable: bool,
}Expand description
How the scheduler must treat one node.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.shape: TileShapeThe shape tiles of this node’s output take.
materialize: boolWhether this node’s whole output must be realized before its consumers pull from it.
Set where demand on this node is not forward-monotonic and the pixels below come from a forward-only source (ADR-0009). It is a property of this position in this pipeline, not of the node’s op.
cacheable: boolWhether this node’s tiles are worth retaining in the tile cache.
Only nodes whose output is genuinely demanded more than once qualify: a shared graph prefix, or a node feeding a spatial op whose tile requests overlap. In a linear pipeline every tile is produced once and consumed once, so caching it would be pure waste — and, worse, would fill the byte budget with garbage and make a streaming pipeline’s memory look like the cache budget rather than a few tiles.