Destructuring: Suppose I have a function like this...

# getting-started

[Mark]

Destructuring: Suppose I have a function like this:

fun childVisible(left: Int, top: Int, right: Int, bottom: Int): Boolean

and I want to pass in the properties of an Android Rect. Is there a way to do the following more concisely?

val (childLeft, childTop, childRight, childBottom) = childRect
return childVisible(childLeft, childTop, childRight, childBottom)

[Adam Powell]

if we're playing golf,

return childRect.run { childVisible(left, top, right, bottom) }

[Adam Powell]

or alternatively with(childRect) { ... } if you don't need the fluent chaining style

[Adam Powell]

but this is a pretty great way to write unreadable code if overused 🙂

[Mark]

Thanks! I think this is better, because now there’s only one chance to screw up the order, rather than two.

[Adam Powell]

might as well make it a function that overloads childVisible though if you're going to use this in enough places where you're worried about getting the order wrong

[Matteo Mirk]

also consider using named parameters to reduce the chance of misplacing actual parameters

[Marat Akhin]

Another option would be to make an extension function on Rect, which calls childVisible with the correct arguments

[Dico]

I may well just use (l, t, r, b)