Struct ComputePipelineRegistry

pub struct ComputePipelineRegistry { /* private fields */ }

Registry for managing and dispatching compute pipelines.

The ComputePipelineRegistry serves as the central hub for all compute pipelines in the Tessera framework. It maintains a collection of registered pipelines and handles the dispatch of compute commands to their appropriate pipelines.

Architecture

The registry uses type erasure to store pipelines of different types in a single collection. When a compute command needs to be processed, the registry attempts to dispatch it to all registered pipelines until one handles it successfully.

Usage Pattern

1. Create a new registry
2. Register all required compute pipelines during application initialization
3. The renderer uses the registry to dispatch commands during frame rendering

Example

use tessera_ui::renderer::compute::ComputePipelineRegistry;

// Create registry and register pipelines
let mut registry = ComputePipelineRegistry::new();
registry.register(blur_pipeline);
registry.register(contrast_pipeline);
registry.register(brightness_pipeline);

// Registry is now ready for use by the renderer

Performance Considerations

• All registered pipelines are called for each command until one handles it
• Register more commonly used pipelines first for better average performance
• Consider the frequency of different compute operations when ordering registrations

Thread Safety

The registry and all registered pipelines must be Send + Sync to support parallel execution in the rendering system.

Implementations

impl ComputePipelineRegistry

pub fn new() -> Self

Creates a new empty compute pipeline registry.

Example

use tessera_ui::renderer::compute::ComputePipelineRegistry;

let registry = ComputePipelineRegistry::new();

pub fn register<C: ComputeCommand + 'static>( &mut self, pipeline: impl ComputablePipeline<C> + 'static, )

Registers a new compute pipeline for a specific command type.

This method takes ownership of the pipeline and wraps it in a type-erased container that can be stored alongside other pipelines of different types.

Type Parameters

• C - The ComputeCommand type this pipeline handles

Parameters

• pipeline - The pipeline instance to register

Example

use tessera_ui::renderer::compute::ComputePipelineRegistry;

let mut registry = ComputePipelineRegistry::new();

// Register custom compute pipelines
let blur_pipeline = BlurPipeline::new(&device);
registry.register(blur_pipeline);

let contrast_pipeline = ContrastPipeline::new(&device);
registry.register(contrast_pipeline);

// Register multiple pipelines for different effects
registry.register(BrightnessAdjustmentPipeline::new(&device));
registry.register(ColorGradingPipeline::new(&device));

Registration Order

Unlike drawable pipelines, compute pipelines are dispatched to all registered pipelines until one handles the command. Consider registering more frequently used pipelines first for better performance.

Thread Safety

The pipeline must implement Send + Sync to be compatible with Tessera’s parallel rendering architecture.

Trait Implementations

impl Default for ComputePipelineRegistry

fn default() -> ComputePipelineRegistry

Returns the “default value” for a type.