Hi folks, are 2 instances of function references not same ? I am calling below Composable ```Permis...

# compose

[aishwaryabhishek3]

Hi folks, are 2 instances of function references not same ? I am calling below Composable

PermissionsScreen(
    Modifier.padding(innerPadding),
    uiState,
    viewModel::onAction,
)

I see that whenever recomposition happens because of changing uiState, the function reference is also a different instance from previous one which causes more recomposition for Composable which should not be recomposed.

[Zoltan Demant]

Afaik, this happens because your function references the viewmodel, which is considered unstable. You could test adding @Stable to your viewmodel to verify what Im saying, Im pretty sure it wouldnt result in new functions everytime that way.

[aishwaryabhishek3]

@Zoltan Demant I marked viewModel as stable but the issue persists, the only way seems to be to wrap the fun ref in a remember 😕 .

[Olivier Patry]

I used to store the function references before entering the Compose world (before setContent) and then pass these variables down to my screens to solve this.

class Activity... {
  private val viewModel by viewModels()
  fun onCreate(...) {
    val foo = viewModel::foo
    setContent {
      MyTheme {
        Surface {
          MyScreen(viewModel, foo)
        }
      }
    }
  }
}

[shikasd]

Two instances of function references are not the same specifically because function reference can be to a local function and that can go wrong very fast

That being said, with strong skipping this no longer should be a problem, not sure why it recomposes here