How can I write a program that compiles without warnings?

Question

I tried the following with the 1.5 beta-compiler (build 28; I think):
class Y {
     public static final class Pair<X,Y> {
       private X fst;
       private Y snd;
       public Pair(X fst, Y snd) {this.fst=fst; this.snd=snd;}
       public X getFirst() { return fst; }
       public Y getSecond() { return snd; }
       public String toString() { return "("+fst+","+snd+")"; }
  public static void main(String... args) {
     Pair[] pairArr = new Pair[10];              // supposed to be an array of Pair<Integer,Integer>
     for (int i=0; i<pairArr.length; i++)
         pairArr[i] = new Pair<Integer,Integer>(i,i);
     for (int i=0; i<pairArr.length; i++) {
         Pair<Integer,Integer> p = pairArr; // unchecked warning
     System.out.println(p);
     Integer first = p.getFirst();
     Integer second = p.getSecond();
// ... more stuff ...
It turns out that I get an unchecked warning when I extract an element from the array of pairs. Okay, that's fine. How can I avoid the warning? I had expected that an explicit cast would help.
  Pair<Integer,Integer> p = (Pair<Integer,Integer> )pairArr;
With a cast I'm telling the compiler: "I _know_ what I'm doing; please trust me." But the compiler still issues a warning.
How can I write a warning-free program in this case? The only thing I can think of, is not using the parameterized type Pair in its parameterized form. But it's not the idea of Java Generics that I refrain from using parameterized types. What am I missing?

Answer 1

It turns out that I get an unchecked warning when I
extract an element from the array of pairs. Okay,
that's fine. How can I avoid the warning? I had
expected that an explicit cast would help.
Pair<Integer,Integer> p = (Pair<Integer,Integer>
)pairArr;
With a cast I'm telling the compiler: "I _know_ what
I'm doing; please trust me."  But the compiler still
issues a warning.  Yes, but at least you were able to change the warning from "unchecked assignment" to "unchecked cast" which is a little shorter ;-)
Seriously , since arrays of generic types are disallowed, there is probably no way to get rid of these warnings - which makes a strong point for eliminating "unchecked" warnings altogether (see the other thread "selectively suppressing compiler warnings")
Cheerio,
Gernot