Is there a reason `Layout` composable function has...

# compose

[orangy]

Is there a reason Layout composable function has content parameter first and not last, so it would allow for container-like invocation?

[Zach Klippenstein (he/him) [MOD]]

You can specify the parameters in whatever order you want if you name them

[Javier]

but that forces to specify all names except content one to get the container invocation

[orangy]

I can’t invoke it like Layout(measureBlocks) { … } in named parameters form

[orangy]

Oh, I got it. Confused by a different overload. MeasureBlock is a lambda typealias

[Adam Powell]

yes, the intended usage here is for implementing a custom layout composable, e.g.:

@Composable fun MyLayout(
  modifier: Modifier = Modifier,
  content: @Composable () -> Unit
) = Layout(content, modifier) { measurables, constraints ->
  // measure logic here
  layout(myWidth, myHeight) {
    // placement logic here
  }
}

[Adam Powell]

so the measure/layout DSL block gets the trailing lambda position