-
Notifications
You must be signed in to change notification settings - Fork 137
Misc. changes #940
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
Misc. changes #940
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #940 +/- ##
==========================================
- Coverage 91.84% 88.25% -3.59%
==========================================
Files 37 62 +25
Lines 4976 8668 +3692
Branches 0 1049 +1049
==========================================
+ Hits 4570 7650 +3080
- Misses 406 1018 +612 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as a checklist, I guess it's everything non-static in manifold.h
that returns a Manifold
?
Thinking about it, some functions in |
Notably, |
I was looking into other functions that do unary operations on a manifold. Apparently, they copy the |
maybe I will fix the wasm issue tmr |
IIRC, the manifold is set to empty when any of the error conditions occur - at least that was the intention. So I believe that yes, they should all be in a safe state. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Fixes #744.
I don't plan to do 64-bit run ID or mesh ID, as I don't think users will ever want that...? It might make sense in some scientific computation situation to handle large meshes, but it doesn't make sense to do boolean on several hundred million meshes, I guess...
Checklist for error propagation, feel free to add to this list, so I can add them in this PR: