removed cross_section dependency from manifold #850
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is one of several steps toward #803, and specifically addressing #664 (comment). Now Manifold has no direct dependence on Clipper2 - Clipper2 is only a dependency of CrossSection (2D), which is independent of Manifold (3D). We rely only the very simple
Polygons
class as an interface between these libraries, akin toMesh
.Since we build our Python and JS bindings with Manifold and CrossSection bundled together, I'm keeping their APIs from changing, so they still accept and return
CrossSection
instead ofPolygon
, since that feels a little nicer.