A modern programming language that makes developers happier.

kotlinlang

Here's a question about best practices... I know that Kotlin does away with the 1 public class per source file requirement that Java has, as well as the requirement than the name of the file match the public class. For an existing Java project that's slowly incorporating Kotlin, what are your thoughts on taking advantage of this (or not)? My particular use case is a set of data classes that comprise an object graph. There's about 4 classes, with about 3 of them being one-liners. It seems odd to use an entire file on a one line class, so I'm tempted to define the entire hierarchy into the same file. But then again I'm anticipating having to defend this decision and I'm finding myself unsure. Thoughts/pointers?