Implement operator overloads

I have a math vector class used across the renderer and physics. Implement operator+ and operator+= so adding vectors is consistent. Make operator+ call operator+= internally, ensure exception safety, and preserve component-wise semantics. Add tests showing both operators for temporary and lvalue operands. Ladder L1

Before I expose arithmetic operators on the vector type to the rest of the engine, make the interface easy to review by the physics lead. Show the public signatures up front, ensure operator+ does not allocate, document value-category effects, and flag any conversions that could be implicit and surprising to a reviewer. Ladder L2

I attempted to use my Vector class with code that does position = velocity + acceleration * dt and the compiler reports ambiguous overloads between operator+ and a templated free function. I cannot tell which overload the caller expects and whether temporaries will be moved. What is the likely cause and what minimal changes should I make so addition is unambiguous, efficient for temporaries, and safe for the physics code? Ladder L5

Across the codebase we have several small math types with slightly different operator overload patterns; some use member operator+, others free functions, and some return by value while others return proxies. This causes ambiguous calls and performance cliffs. What habit should the team adopt for operator overloads, how to refactor gradually, and what tests or code-review rules will prevent the class of bugs going forward? Ladder L6