4 ms·
Exactly. Every programming language out there has some cases where you can break the established rules by doing weird stuff. When this sort of thing happens, th
by ARandumGuy 5y ago
Exactly. Every programming language out there has some cases where you can break the established rules by doing weird stuff. When this sort of thing happens, there's two things to look at:
1) Is this likely to happen by accident?
2) Does this enable some functionality not otherwise available (even if it's still a bad idea)
Looking at the paper, it seems like neither of these is the case for Java/Scala types. Given that, I would categorize this as a weird quirk of Java and Scala, and leave it at that.
- Gunax 5y agoI dont think this has to be true. We shouod be able to build perfectly logical and deterministic type systems--and ny understanding is that Java was unambiguous before generics were added.
- hyperman1 5y agoI'd guess ARandumGuy has the soul of an engineer. Confronted with an imperfection, the question is how bad it is in a world full of even bigger imperfections. Is it worth the time,effort and resources to fix it? Gunax has the soul of a mathematician. Confronted with an imperfection, the question is how to eradicate this blight from the world and get us one step closer to perfection, no matter the cost. Both are equally correct reactions, of course. Just nice to see them in the same place.