Is there any point in declaring a class with "concrete" types as generics?
If yes, what's the use for it?
If no, any specific reason why the compiler is allowing it?
The code:
public class SomeClass<Integer> {
//...
public static void main (String a[]) {
// SomeClass <> iSome = new SomeClass<>();
// SomeClass <Integer> jSome = new SomeClass<>();
SomeClass <Double> kSome = new SomeClass<>();
// ...
}
}
is running fine, and is giving compiler errors when I uncomment the lines declaring iSome and jSome.
I'm trying to put things together in "deciphering" the generics.
Thanks in advance.
It's not what you think. You're creating a generic type parameter called Integer which shadows java.lang.Integer.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With