Today in private method I used Long.parseLong() (just once in whole class) with some String as value. At peer review colleague wrote that this method should be static import and then called without Long.. I asked why because as I know and what is in https://stackoverflow.com/a/421127/4952262 in such case we should just go with Long.parseLong() instead of trying to save 5 characters. The answer was that parseLong method is just in Java.lang.Long package and it's safe because this method was, is and will be just in this package. Is it good way? Does it really make a code more readable?
Static import Long.parseLong in Java
Viewed 338
1 Answers
It depends how do you infer it, I have read a lot about it that static imports increase the code readability.
But let's think of a scenario where you have two classes namely Class A and B.
Think that both the classes have similar static fields/method that you want to use in some third Class C.
Now how does it increase the readability of code ?
Again i am not arguing where its wrong or correct to use static imports but yes i do believe in some of the cases it sounds good to do so in other it might not.
Note : Anyways it does not make any difference when it comes to performance as much as i know.
Related