4 ms·
The industry perspective is that nobody cares (and rightly so). I was at the conference where this was presented. The paper is terrifically written, and it's g
by norswap 10y ago
The industry perspective is that nobody cares (and rightly so).
I was at the conference where this was presented. The paper is terrifically written, and it's good that someone is investigating this.
That being said, it's just not that big of a deal. In practice, this will never be a problem for anyone writing Java.
The Java wildcard system is insane and no-one is trying to build type systems based on these ideas, not even Scala and the new batch of JVM languages (Kotlin, Ceylon). They have their own problems, but this isn't it.
- nerdwaller 10y agoAgreed no one in practice will likely ever see this. Ability to compile vs warned about it are two different things. Those that know Java would quickly be aware that a) type erasure is a thing, it allows stuff like this b) even if they wrote some of this their IDE or compiler would generate a ton of warnings. Generally when you have a compiler - you learn to look at the output of it.
- zaphar 10y agoGenerally when your compiler spits out a lot of warnings you learn to ignore them.