Why is this HashMap declaration using generics wrong?

Question

HashMap<String, ArrayList<? extends Serializable>> map = new HashMap<String, ArrayList<ArrayList>>();

This does not compile. To the best of my knowledge on Java Generics, it should. And this:

ArrayList<? extends Serializable> c = new ArrayList<ArrayList<String>>();

successfully compiles.

Can anyone say why the above wouldn't compile?

Strongly related: [Java nested generic type](https://stackoverflow.com/questions/22806202/java-nested-generic-type) — rgettman, Mar 02 '18 at 02:00
The fact that `A` extends (or implements) `B` doesn't imply that `HashMap` extends `HashMap`. After all, a `HashMap` is something that you can put a `B` in, but a `HashMap` isn't. Equivalent questions have been asked before. — Dawood ibn Kareem, Mar 02 '18 at 02:12

Andrey Tyukin · Accepted Answer · 2021-11-08T08:39:51.047

Why do you think that it should? A HashMap<String, Apple> is never assignable from a HashMap<String, Orange> for any possible unequal Apple and Orange, as long as both Apple and Orange are not wildcard-types.

And ArrayList<? extends Serializable> is not the same thing as ArrayList<ArrayList<?>>.

What you probably meant:

HashMap<String, ? extends ArrayList<? extends Serializable>> map = 
  new HashMap<String, ArrayList<ArrayList<?>>>();

Now it compiles, because indeed:

? extends Serializable // can be assigned from
          ArrayList<?>

and

? extends ArrayList<? extends Serializable> // can be assigned from
          ArrayList<          ArrayList<?>>

Thanks, I took your advice and it indeed works now. – Miy Mar 19 '18 at 11:03 — Miy, Mar 19 '18 at 11:03

Why is this HashMap declaration using generics wrong?

1 Answers1