Bug 333119 - Equality operators for track related classes
Review Request #117416 - Created April 7, 2014 and submitted
Added operator== and operator!= to the classes GeoDataTrack and GeoDataMultiTrack. Extended TestEquality by a new unit test method for each class which verifies the implementation for several instances of each class.
Wouldn't this one trigger if the sizes differ?
You cannot work on m_line string* here because of the lazy update logic. Instead compare lineString() to other.lineString() and ideally also Q_ASSERT on the needsUpdate variables being false both after calling lineString(). Alternatively ignore both variables in the equality check since they provide redundant data.
Review request changed