New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanups and iterator #5
Cleanups and iterator #5
Conversation
…ontour.segment() We add #[derive(PartialEq)] to Segment2 so that they can be compared with == to each other.
It seems to have been forgotten?
It's used in code that is commented out
Other names were already in snake_case; if you really want the former you can use #![allow(non_snake_case)] in the module toplevel.
Hey, thanks for cleaning up stuff I'd been putting off :) |
Thanks for the merge! I'd like to continue cleaning this up, but I'm not sure about some things:
|
Hm, I don't know if much more cleanup is really worth it (or possible!) until I figure out exactly what I want this to do for an 0.1 release and get it working — there are a whole lot of things started on but not finished. I do welcome any feedback on stuff I start doing, though, and tests are certainly a good idea... |
This pull request has several things:
shapeops::compute()
now takes a slice, not a&Vec
.Contour::iter_segments()
return something that implementsIterator
, instead of copying a new vector.iter_segments()
forcargo test
.do_flip()
in the main program; I think this was just an oversight?