Skip to content

Conversation

@nicoburns
Copy link

An experiement in making a base vocabulary crate to sit under kurbo (could also be used in parley, peniko, taffy, etc. This crate is similar to euclid, except that it doesn't have a type parameter for the units making it much more ergonomic to use.

The idea is that this crate would be highly stable (rarely if ever making breaking changes).

Tasks

  • Duplicate kurbo crate as bazo
  • Remove kurbo-specific code from bazo
  • Make bazo types generic (rather than hardcoded to f64)
  • Use bazo types in kurbo and ensure all impls still work

Open questions

  • Is this a good idea?
  • Should Stroke, Cap, Dash, etc be included (in limited form)?
  • Should BezPath, CubicBez, QuadBez (in limited form)?
  • Where should the kurbo SVG path parsing code live (separate crate?)
  • Should this depend on num-traits or have it's own number abstractions?

Signed-off-by: Nico Burns <nico@nicoburns.com>
@nicoburns nicoburns added needs discussion This change requires some more discussion before we decide we definitely want it in progress Someone is working on the issue, or a related PR is waiting for review labels Sep 27, 2025
@nicoburns nicoburns marked this pull request as draft September 27, 2025 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in progress Someone is working on the issue, or a related PR is waiting for review needs discussion This change requires some more discussion before we decide we definitely want it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant