The current collision logic has two flaws:

• collisions are only checked at the positions of the vehicle, i.e., we take short-cuts by jumping over curves if we are fast enough
  • resolve this by checking on multiple points along the current and previous position
• the method check_collision of Vehicle class resets the Vehicle
  • this behavior is unexpected behavior (given the name of the method)
  • the method should just return a bool
  • the vehicle should be reset outside of this method

Moving towards vehicle-vehicle collisions

As of now, we are only implementing vehicle-track collisions. If we want to handle vehicle-vehicle collisions, then we have to answer the following question:
Who is in charge of checking (what types of) collisions?

• is it each Vehicle?
• is it the Race instance?
• is it the App instance?