In Diagrams a Path is a list of Located Trails with a compose monoid. To do this, I think the current Path functionality can be moved to Trail, with a .at() function to create a path.
While doing this, Trail should have a second argument that says whether it is a Closed, and a way to locate the trail separately. (In Haskell they do this in the type system, which seems like just showing off.)
(this is lo-pri, just noting so that we don't get out of sync with the main library).
In Diagrams a Path is a list of Located Trails with a compose monoid. To do this, I think the current Path functionality can be moved to Trail, with a .at() function to create a path.
While doing this, Trail should have a second argument that says whether it is a Closed, and a way to locate the trail separately. (In Haskell they do this in the type system, which seems like just showing off.)
(this is lo-pri, just noting so that we don't get out of sync with the main library).