Why are java collection classes declared with redundant interfaces?

public class HashMap<K,V>
extends AbstractMap<K,V> implements Map<K,V>, Cloneable, Serializable

Here, the part that implements Map is not needed, since AbstractMap already implements Map. Why do all similar collection class declarations have this redundancy?

+4
source share

Source: https://habr.com/ru/post/1570774/


All Articles