On the other hand if you're asking about the ovrriding vs not overriding I can see that if not overridden the JVM has to scan the class hierarchy to find the instance to call, but I would expect that to be very fast and negligable.
On Mon, Dec 1, 2014 at 2:04 PM, Claude Warren <[email protected]> wrote: > Andy, > > I can find no documentation that indicates that the @Override speeds up > processing. All documentation that I have found on @Override indicates > that it is a hint to the IDE to let the user know when changing a signature > may be an issue in large and complex classes. Infact the Override > annotation is marked as having a retention of "Source", so I don't see how > it could play a role in runtime evaluation. > > Claude > > On Mon, Dec 1, 2014 at 1:44 PM, Andy Seaborne <[email protected]> wrote: > >> >> I see ava.time.chrono.LocalDateTime: >> >> @Override // override for Javadoc and performance >> public String format(DateTimeFormatter formatter) { >> Objects.requireNonNull(formatter, "formatter"); >> return formatter.format(this); >> } >> >> which is overriding the interface ChronoLocalDate which has a default >> method >> >> default String format(DateTimeFormatter formatter) { >> Objects.requireNonNull(formatter, "formatter"); >> return formatter.format(this); >> } >> >> >> How much performance difference does this make? >> >> Andy >> > > > > -- > I like: Like Like - The likeliest place on the web > <http://like-like.xenei.com> > LinkedIn: http://www.linkedin.com/in/claudewarren > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
