Skip to content

sparse_strips: Move filter handling logic from vello_cpu to vello_common#1446

Open
laurenz-canva wants to merge 8 commits intomainfrom
laurenz/move_filters
Open

sparse_strips: Move filter handling logic from vello_cpu to vello_common#1446
laurenz-canva wants to merge 8 commits intomainfrom
laurenz/move_filters

Conversation

@laurenz-canva
Copy link
Contributor

Since this is a relatively isolated change, I decided to open a PR for this now so that it reduces the diff of follow-up PRs. All this PR does is simply:

  • Moving all of the filter definitions that can be reused across both renderers into vello_common, while leaving vello_cpu specific logic where it currently is.
  • Introduce an InstantiatedFilter abstraction that allows instantiating a filter for a specific transform, since we need the same in vello_hybrid.

There's a bit of a question whether we can deduplicate some of the predefined SVG filters and their instantiated versions, but for now this is the least invasive change, I think.


/// A filter that has been instantiated for a specific affine transformation.
#[derive(Debug)]
pub enum InstantiatedFilter {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps PreparedFilter would be a better name?

@laurenz-canva laurenz-canva changed the title Move filter handling logic from vello_cpu to vello_common sparse_strips: Move filter handling logic from vello_cpu to vello_common Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments