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.
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
Parry benchmarks compilation #255
Parry benchmarks compilation #255
Changes from 2 commits
7e50bf0
7e76ebe
d6df1e8
27fee28
e835b59
e60d618
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
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.
ConvexHull
is no longer a type as iitself, but rather an alias toVec<Point<Real>>
, I think it would have value to be its own type, but slightly out of scope for this PR.@sebcrozet I'd appreciate instructions as how to proceed:
Should I straight up remove that code, or keep it in and create a tracking issue (+ comment) ?
Then, should I either:
Vec<Point<Real>>
, which will probably be confusingConvexHull
type. An opportunity for better docs in my opinion,ConvexHull
exists in the current documentation at a few places ([here](i.e: https://github.com/Vrixyz/parry/blob/7e76ebe0c7a155e44d631d4f25a227cf7daf598c/src/query/closest_points/closest_points_support_map_support_map.rs#L8) or there...)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.
The
ConvexHull
shpe type has been renamedConvexPolyhedron
in 3D andConvexPolygon
in 2D.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.
Why was that change needed?
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.
using
drop
results in a warning:Aabb
andBoundingSphere
are concerned. I don´t think this is an opportunity to make benchmarks more accurate (if we're unexpectedly copying).Actually I'm not exactly sure why this drop is necessary. As we're in an unsafe call, I guess it might be useful, but not really used in current usage. It doesn´t hurt being here I guess.