MechanicalWorld and migration from v0.11
Open
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
I notice that `DefaultMechanicalWorld` is not really a replacement for `nphyics3d::world::World` from v0.11 but rather a sub-set. Whatever reason the geometry/collider world, body, collider, joint and force sets are now separate, the examples show that these often do not need to be used separately.
Is it worth adding a type akin to the old `World` to wrap all the above (and likely also ease migration from v0.11)?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.