Not a big issue, but I have been thinking about how the warm start check that blocks and bodies match for a contact in the last time step with one identified in this time step involves building a string and a string compare, as opposed to checking the object IDs.
Another thought is that with the BodyContact objects (can this name be refactored / improved) storing information on the contacts between two rigid bodies, it can be a faster map lookup to check only those for the same pair of contacting bodies... Perhaps a silly optimization given that hashmaps and treemaps are so fast. And there are much bigger fish to fry.
Not a big issue, but I have been thinking about how the warm start check that blocks and bodies match for a contact in the last time step with one identified in this time step involves building a string and a string compare, as opposed to checking the object IDs.
Another thought is that with the BodyContact objects (can this name be refactored / improved) storing information on the contacts between two rigid bodies, it can be a faster map lookup to check only those for the same pair of contacting bodies... Perhaps a silly optimization given that hashmaps and treemaps are so fast. And there are much bigger fish to fry.