Skip to main content

Module render

Module render 

Source

Re-exports§

pub use until::Until;

Modules§

until

Structs§

Block
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. The target may read @notes, the sum of the terms added under handles. A node the store answers plays from its samples. A hit is looked up once; a node reading the stream’s own note sum never, as no store holds one.
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, holding the stream only to apply it, between two blocks, once the store answered what it brings in: an exact stream pulled only once its edit is done plays it where it was 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.
plan
The range and every value a render of target would compute, and no sample.
render
Nothing is materialized that no reading asked for.
render_through
render through store, from the root down: a node the store answers stands as its samples, and nothing under it is typed, planned or looked up. What the rest computes is staged beside the store as the render drops it; only persist writes the store. A failing store fails no render: it stages nothing more, and its stats say why.
sketch_atom
One atom as the six factors it is present in, which is what atoms answers with.
warm
render_through’s staging alone, config asking nothing: a stored root ends it unread.