Cleanup TODOs and collision coverage #2286
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cleanup TODOs and collision coverage
remove rerun example wiring now that sources are gone
clarify GCC13 warning suppression rationale and avoid duplicate flags
enforce component dependency targets and export generation guards in CMake helpers
better host arch detection for SIMD flags on non-x86 builds
expand collision detector parametrization in python tests and move meta skeleton to integration
clarify C-prefix STL header sorting rule in clang-format
Run
pixi run test-allto lint, build, and test your changesAdd unit tests for new functionality
Document new methods and classes
Add Python bindings (dartpy) if applicable