On Wed, 22 Sep 2021 19:14:03 GMT, Andrey Turbanov
wrote:
> In several places, String.compareTo was _compared_ with 0 ( via `== 0` or `!=
> 0`).
> Instead of this, we can use String.equals calls. `String.equals` is faster
> and shorter.
Looks good.
Thanks,
Serguei
-
Marked as rev
On Wed, 22 Sep 2021 19:14:03 GMT, Andrey Turbanov
wrote:
> In several places, String.compareTo was _compared_ with 0 ( via `== 0` or `!=
> 0`).
> Instead of this, we can use String.equals calls. `String.equals` is faster
> and shorter.
Marked as reviewed by amenkov (Reviewer).
-
On Wed, 22 Sep 2021 19:14:03 GMT, Andrey Turbanov
wrote:
> In several places, String.compareTo was _compared_ with 0 ( via `== 0` or `!=
> 0`).
> Instead of this, we can use String.equals calls. `String.equals` is faster
> and shorter.
Looks good. Make sure you have done the appropriate testi
In several places, String.compareTo was _compared_ with 0 ( via `== 0` or `!=
0`).
Instead of this, we can use String.equals calls. `String.equals` is faster and
shorter.
-
Commit messages:
- [PATCH] Use String.equals instead of String.compareTo to check String's
equality in jdk.j
