I have a private method in an inner class which is private I would like to use the SafeVarargs annotation. However, I am required to either have a static or final method. Why does a private method need to be final as well? Isn't this redundant?
Since private methods are inaccessible, they are implicitly final in Java. So adding final specifier to a private method doesn't add any value.
So, to answer question 2, yes, all compilers will treat private methods as final . The compiler will not allow any private method to be overridden. Likewise, all compilers will prevent subclasses from overriding final methods.
It is redundant, and you bring up an excellent point.
I think the real reason for the requirement of final or static was to force that the method could not be overridden, and thus a subclass couldn't tamper with data in a way that made the @SafeVarargs annotation useless on the definition of the method.
But, although it is redundant, it's not that bad of a decision - many a time, programmers will make every method private as much as possible, and then slowly open the class up as needed. If this method is marked final when it is in private scope, then if the method has to be opened up, it can still have the @SafeVarargs annotation in place with only a change to the access level. If the final is removed intentionally, you'll get the compile time error, but if you had it already, whoever removes the private access (which may not be yourself, in a team-based environment) won't be confused as to why removing the "private" modifier suddenly makes the code no longer compile.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With