Benjamin Saunders

> Do you have any idea how to workaround also this? Does the usual ```rust let remaining = self.remaining(); buf.advance(remaining); ``` trick not apply here for some reason?

Ah, I see. I think what you want is reasonable, and is basically a more generic version of `Bytes::split_to`. The proposed signature has a drawback though: the returned `&[u8]` will...

Tests pass fine locally, so I'm guessing the CI is just broken, though the `Details` link doesn't work...

> The internal contact generation method (often named do_update) need to know if its argument were flipped so it can generate the contact manifolds with the right arguments order. Good...

Semi-related: dimforge/rapier#324 (that issue should maybe have been opened here instead).

I believe that convex hulls have a well-defined interior, i.e. a shape will be considered colliding if it lies within a convex hull even if it does not intersect the...

Given the potential complexity and diversity of dispatch logic, maybe the most pragmatic option is to define something like ```rust pub trait Dispatcher { fn get(&self, a: &dyn Shape, b:...

> put dyn in front of every trait object, thereby making them easily recognisable. This was ~250 changes and originally meant only for development purposes but I think it is...

The entirety of serialization support should be an optional feature, since serde is a large dep that is not universally required.

This could be solved well by replacing the two callbacks with a trait object: ```rust trait BroadPhaseFilter { fn allow_proximity(&mut self, &T, &T) -> bool; fn proximity_handler(&mut self, &T, &T,...