Weird. I have a naive forEach function on a "custom collection" like thing, that hides its internals...

# compose

[Travis Griggs]

Weird. I have a naive forEach function on a "custom collection" like thing, that hides its internals:

fun forEach(closure: (ValveSpan) -> Unit) {
   series.forEach(closure)
}

If I use this in a @Composable function and try to do a @Composition (Text) inside of the closure, the compose compiler won't do it (@Composable invocations can only happen from the context of a @Composable function). Using the stock forEach on normal collections is fine. Do I need to declare my custom forEach with some kind of annoation for compose to be happy using it?

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

You need to make your function inline

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

This is the same reason you can call suspend functions from a forEach on eager collections in a suspending context

[Travis Griggs]

i tried that. unfortunately, the whole reason I added that was that it's a private var it's enumerating, and inline and private vars do not mix apparently?

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

inline literally means it inlines the function body into the call site. So if the call site couldn’t access a private var, an inline function can’t

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

That’s also why it propagates the caller’s “color” – it’s not actually allocating a lambda for the parameter, just copying the function body into the caller.

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

One way to work around that is to make your private property @PublishedApi internal

[Travis Griggs]

thanks, that works