OK. Despite our deep interest in version strings, we rarely use Runtime.Version.
On Thu, Jul 19, 2018 at 12:42 PM, Tony Printezis <tprinte...@twitter.com> wrote: > Hi Martin, > > Yes, we have also used the opt field too. However, if I understand the > spec correctly, when doing version comparisons, the opt string is compared > alphanumerically. So if you add any numbers to it, you have to plan ahead > and pad with enough 0s to make sure the comparison works as expected. Given > that the spec now allows extra numbers in the version string, it’d be good > to be able to use that instead. > > Additionally, we want both compareTo() and compareToIgnoreOptional() to > show our version as different to the upstream one it’s synced up to. And > adding an extra number to the version string satisfies that too. > > Other folks might want this to behave differently, and that’s totally OK! > But, the change I proposed will help anyone who has the above requirement. > >
