Skip to content

Conversation

thiemowmde
Copy link
Contributor

@thiemowmde thiemowmde commented Aug 10, 2017

Together with #115 this will allow us to remove an other giant chunk of the formatting logic.

Note that I intentionally changed this code in a way that no test needed adjustment. (And there are quite a lot of test cases.) The / 2 division makes sense when you think of it this way: Let's say the first coordinate is given as 173°, and the second as 173.5°, both with a precision of 1°. This means the first is rendered as "173°", but the second as "174°". Because of this they must be considered unequal, even if the difference between the two is only 1/2 of the precision.

Bug: T172916

@thiemowmde thiemowmde added this to the 0.9.0 milestone Aug 10, 2017
@thiemowmde thiemowmde requested a review from Ladsgroup August 10, 2017 22:46
@thiemowmde thiemowmde mentioned this pull request Sep 1, 2017
@thiemowmde thiemowmde mentioned this pull request Oct 4, 2017
@thiemowmde thiemowmde requested a review from manicki October 4, 2017 14:39
@thiemowmde thiemowmde mentioned this pull request Oct 5, 2017
@lucaswerkmeister lucaswerkmeister merged commit 448214c into master Oct 6, 2017
@lucaswerkmeister lucaswerkmeister deleted the coordinateEquality branch October 6, 2017 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants