8000 removed cross_section dependency from manifold by elalish · Pull Request #850 · elalish/manifold · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

removed cross_section dependency from manifold #850

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

Merged
merged 4 commits into from
Jun 27, 2024
Merged

Conversation

elalish
Copy link
Owner
@elalish elalish commented Jun 16, 2024

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 to Mesh.

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 of Polygon, since that feels a little nicer.

@elalish elalish self-assigned this Jun 16, 2024
@elalish elalish added the breaking change API changes for major versions label Jun 16, 2024
@elalish elalish requested review from pca006132 and geoffder June 18, 2024 22:29
Copy link
Collaborator
@pca006132 pca006132 left a comment

Choose a reason for hiding this comment

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

LGTM. I think we can also add a Markdown document for the list of breaking changes implemented, so it is easier for users to follow.

return Invalid();
Polygons polygons;
float radius = 0;
for (const SimplePolygon& poly : crossSection) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

It seems that our only non-trivial change is here. Do we have test cases that can cover it? While the logic is simple, it is easy to have bugs here.

Copy link
Owner Author

Choose a reason for hiding this comment

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

Indeed - yes this originally came in from an external contributor who put in test cases for it, so I think we're covered.

@pca006132
Copy link
Collaborator

I think we can just merge this?

@elalish elalish merged commit 85d71f5 into master Jun 27, 2024
18 checks passed
@elalish elalish deleted the separateCrossSection branch June 27, 2024 19:19
@elalish elalish mentioned this pull request Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change API changes for major versions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0