Avoid fishy reference equality on strings
Avoid fishy reference equality on strings

While the code looks correct (because strippedName comes from stripSuffix and because of stripSuffix's contract and implementation), this is subtle enough that we should either add a test or use !=.

Since `String.equals` happens to be O(1) in this case, changing the code looks simpler. `String.equals` is O(1) here because it will either succeed by testing pointer equality or fail by noticing a length mismatch, so it will never look at the actual contents!
lampepfl/dotty,sjrd/dotty,lampepfl/dotty,som-snytt/dotty,lampepfl/dotty,dotty-staging/dotty,lampepfl/dotty,sjrd/dotty,sjrd/dotty,dotty-staging/dotty,dotty-staging/dotty,som-snytt/dotty,som-snytt/dotty,dotty-staging/dotty,dotty-staging/dotty,som-snytt/dotty,sjrd/dotty,lampepfl/dotty,som-snytt/dotty,sjrd/dotty