Is there a reason

androidx.compose.ui:ui-util:1.0.0-rc02

includes a

fastMap()

but not a

fastMapIndexed()

function? Would it be the same as if using kotlin std lib's

mapIndexed()

?

Didn't think people actually used those micro optimized

fast

functions.

I came across them today, while checking some standard Compose code. They supposedly avoid allocating iterators, so I guess they don't trigger garbage collection during composition as much. I don't know if they worth the fuss, though, so this is why I am asking.

they're worth the fuss in some very hot code paths that we identified by measuring and profiling in both macro and microbenchmarks. Don't worry about it unless/until you measure specific issues in your app.