3 ms·
No, in fact you frequently have more when you start using case classes. Plus you frequently have the companion object that goes with your class that acts as a
by mason55 13y ago
No, in fact you frequently have more when you start using case classes. Plus you frequently have the companion object that goes with your class that acts as a singleton.
- kasey_junk 13y agoI understand the limitations of Scala with regard to class/trait/objects etc. What I'm asking is if it is still an issue in Java 8? I'm shocked every time I drop back into java land that people haven't revolted against this terrible requirement.
- edwinnathaniel 13y agoWhy is this an issue or a big deal? Really.
- kasey_junk 13y agoBecause it adds friction between separating implementation and interface. That is one of those things I want to be as seamless as possible. Is it a big deal in the case of 1 interface and 1 class? No not really. But in the case of thousands of them it becomes an issue. It's actually one of the biggest things I notice when I come back to java land.
- edwinnathaniel 13y agoI think with modern Java libraries (and testing libraries as well), the days of 1:1 interface=>classes are almost gone. I rarely do that any more these days so hopefully it'll become non-issue in the future for you.
- mason55 13y agoOh, yes, in Java it's still one class per file