pbenedict at apache.org
Tue Aug 7 17:38:18 PDT 2012
On Tue, Aug 7, 2012 at 7:00 PM, Rémi Forax <forax at univ-mlv.fr> wrote:
> From a design point of view, I feel this is wrong because the traits
> will expose its implementation and it's better to let the concrete class
> that implements the interface at the end to decide how a concept should
> be implemented.
> An interface with default methods is a way to expose a set of abstract
> method plus some default methods implementing the default behavior.
> By example, Map.Entry, is conceptually a pair of value, the default
> methods should provide a useful toString()/hashCode and equals to avoid
> people that implement it to forget that this interface also requires a
> contract on object methods.
Except it is now illegal to have override-equivalents of any
More information about the lambda-dev