> On May 8, 2020, at 1:11 PM, Kirk Lund <kl...@apache.org> wrote: > > I want to avoid having Java Interfaces in which every method (or even many > methods) has a default empty implementation. I think that's ok for callback > interfaces like CacheListener, but it's horrible for interfaces like Cache, > Region, InternalCache, InternalRegion. I don't think these non-callback > interfaces should have any default empty implementations. +1
Even for callbacks I would prefer interface without defaults until a new method is added. If you want to have a no-op implementation that is what an abstract class is for. -Jake
