为何用List接口初始化LinkedList后调用addFirst需强制转换？

Let me break this down clearly for you:

1. Interface vs. Implementation in Java

   • The List interface defines a core set of methods that all list implementations (like LinkedList, ArrayList, etc.) are required to support—think add(), get(), size(), and so on.
   • However, addFirst() is not part of the List interface; it’s a method unique to LinkedList, tailored to its doubly-linked list structure where adding elements to the head is a native, efficient operation.

2. Variable Type vs. Underlying Object

   • When you write List<Node> optimal = new LinkedList<>();, you’re following the "program to the interface" best practice, which gives you flexibility to swap out implementations later. But this also means the compiler only recognizes methods defined in the List interface for the optimal variable—even though the actual object behind it is a LinkedList.
   • At compile time, the compiler only knows optimal is some type of List, not specifically a LinkedList, so it blocks calls to methods outside the List contract.

3. What the Cast Accomplishes

   • By casting ((LinkedList<Node>) optimal), you’re explicitly telling the compiler: "I guarantee this List instance is actually a LinkedList". This lets the compiler access LinkedList-specific methods like addFirst() that aren’t part of the standard List interface.

Alternatives to Avoid Casting #

• If you know you’ll need LinkedList-specific functionality upfront, declare the variable as a LinkedList directly:

  LinkedList<Node> optimal = new LinkedList<>();
  optimal.addFirst(new Node(i, p)); // No cast required!
  

• If you want to stick with the List interface, you can use add(0, new Node(i, p)) to add elements to the front. Just note this is less efficient for ArrayList (but works perfectly fine for LinkedList).

内容的提问来源于stack exchange，提问作者George Waat