* feat: solver improvements
* feat: add function to get/set whether gyroscopic forces are enabled on a rigid-body
* chore: switch to released versions of parry and wide instead of local patches
* fix cargo doc
* chore: typo fixes
* chore: clippy fix
* Release v0.29.0
* chore: more clippy fixes
* feat: reduce the amount of duplicate work the broad-phase is doing for user changes and CCD
* Release v0.28.0
* chore: fix warnings
* chore: clippy fixes
* chore: more clippy fixes
* Replace crossbeam channel with std::sync::mpsc
- Replace all uses of crossbeam::channel with std::sync::mpsc
- Remove crossbeam dependency from all Cargo.toml files
- Update documentation to remove crossbeam references
- Use std::sync::mpsc::channel() instead of crossbeam::channel::unbounded()
Fixes#828🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Update mod.rs
---------
Co-authored-by: Claude <noreply@anthropic.com>
* feat: switch to the new Bvh from parry for the broad-phase
* chore: cargo fmt + update testbed
* chore: remove the multi-grid SAP broad-phase
* fix soft-ccd handling in broad-phase
* Fix contact cleanup in broad-phase after collider removal
* chore: clippy fixes
* fix CCD regression
* chore: update changelog
* fix build with the parallel feature enabled
* chore: remove the now useless broad-phase proxy index from colliders
* fix tests
* update to parry ~main
* use traverse_depth_first
* add example to test intersection
* rely on upstream PR rather than local
* re-enable profiler_ui for examples
* rely on official parry repository
* chore: switch back to the published version of parry
* chore: update changelog
* chore: remove dead code
* fix compilation of rapier3d-meshloader and rapier3d-urdf
* chore: cargo fmt
---------
Co-authored-by: Sébastien Crozet <sebcrozet@dimforge.com>
By using `workspace.lints`, we can configure lints once for
everything (and then inherit it into the various crates).
The lint configuration for `unexpected_cfgs` works in 1.80+
and warns otherwise.
Co-authored-by: Thierry Berger <contact@thierryberger.com>
Implicit features are slated to be removed in a future version
of Rust (2024 edition).
Fixing this exposed 2 instances where the wrong feature was being
checked for `serde` vs `serde-serialize`.
