I know I'm going to get a lot of grief over this, ...

# announcements

[thomasnield]

I know I'm going to get a lot of grief over this, but I'm coming to the conclusion Tuples have a place in Kotlin, primarily for quickly improvising key objects in functional operations. https://github.com/thomasnield/kotlin-statistics/issues/23

[kz]

I missed the conversation but I have also been tempted by tuples. In my scenario it's working with Apache Spark and doing a bunch of small transformations on my way to the actual model object.

[kz]

I have settled temporarily for an explicit Quadruple data class and a small set of function-local named data classes .

[kz]

Definitely gets in the way of readability. In a few places I use scala's tuples but then I lose null-safety.