Skip to main content

Module render

Module render 

Source

Re-exports§

pub use until::Until;

Modules§

until

Structs§

Block
Built
What one change did anew, not what it carried over.
Counts
Handle
Range
Where a target is read, in samples from t = 0. Unstated, the root’s own support.
Render
RenderConfig
Stream
A target rendered block by block off one table, reading @notes, the sum of the terms added. A change builds only what it changed or newly reads; the rest stays as it stood.
StreamConfig

Enums§

Change
An edit, each with the graph that reaches it and all the stream plays.
Changed
A replace or remove answers whether the stream still held its handle.
Placed
Where a term’s sample 0 sits: the stream’s own, or the sample its add lands at.

Constants§

LATEST
The lookups, and the names started silent, a stream keeps of all it made.
NOTES
The node a stream defines as the sum of its terms, for its expression to read as @notes.
STREAMED

Functions§

answer
A closed form answers off its spectral sum and a buffer off its samples; its own Ty decides which, never a flag on the observation.
answer_buffer
One reading off a buffer nothing rendered — an external file, say — under the profile the caller names. Every representation needing the graph behind it refuses here.
change
build’s change, the stream held only while each try runs, between two blocks: an exact stream pulled once its edit is done plays it where issued. build runs again whenever the stream changed under it.
ends
The sample each of roots read bare would end at, None where its support, pruning included, never ends and such a render refuses for it. Typed together, and no sample.
fetch
What the next second of stream reads off memory, as far as one fetch reaches; a block reading samples not ready computes them, or, live, starts them silent.
plan
The range and every value a render of target would compute, and no sample.
render
render_over memory alone. Nothing is materialized that no reading asked for.
render_over
target over tier, from the root down: a node memory answers stands as its samples, and nothing under it is typed, planned or looked up. What the rest computes memory keeps as it says, offered as nodes where a reader may take them; only persist commits them to a disk. A failing disk fails no render: memory writes nothing more to it, and the stats say why.
sketch_atom
One atom as the six factors it is present in, which is what atoms answers with.
warm
render_over’s work alone, config asking nothing: a root memory answers ends it unread.