Is there a reason for the vanilla `SideEffect` not having key args? In the example in the official <...

# compose

[Saiedmomen]

Is there a reason for the vanilla SideEffect not having key args?
In the example in the official docs, you can see that there easily can be extra calls to the analytics.
The LaunchedEffect is great but the suspend block is sometimes not needed and wasteful.

@Composable
fun rememberAnalytics(user: User): FirebaseAnalytics {
    val analytics: FirebaseAnalytics = remember {
        /* ... */
    }

    // On every successful composition, update FirebaseAnalytics with
    // the userType from the current User, ensuring that future analytics
    // events have this metadata attached
    SideEffect {
        analytics.setUserProperty("userType", user.userType)
    }
    return analytics
}

[tad]

The equivalent is

DisposableEffect(key) {
    ...
    onDispose { }
}

[tad]

I assume SideEffect with a key doesn't make much sense to implement as its purpose is to run on every composition.

[Saiedmomen]

yes but then you have the unused onDispose block

[tad]

Yes, in practice it doesn't matter.

[Saiedmomen]

you could have passed no args if you want it to run with every composition

[tad]

It's trivial to write a wrapper:

@Composable
inline fun OneShotEffect(key: Any, noinline block: () -> Unit) {
    DisposableEffect(key) {
        block()
        onDispose { }
    }
}

[Saiedmomen]

yeah that seems nice. But why isn't it in the API?
I keep thinking there should be a deeper reason for it :)

[tad]

Probably to discourage side-effects 🙂

[Saiedmomen]

Maybe extra suspending is super cheap?

[tad]

LaunchedEffect schedules its block on the main dispatcher, so its changes will always be reflected at least one frame later

[Saiedmomen]

I don't see very use cases for the SideEffect at all.
You almost never want an effect to repeat on each composition

[tad]

It's useful when you want to update a remembered state object through function parameters

[Saiedmomen]

why not just use remeber(arg) {} ?

[tad]

that would recreate the object when arg changes

[Saiedmomen]

Can you please give a short snippet of how that would work?

[Saiedmomen]

never mind. I got it 👍

[Rick Regan]

Check out the conversations in which these two comments appear:

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1639692619286600?thread_ts=1639688997.283600&amp;cid=CJLTWPH7S

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1647206404442389?thread_ts=1647192578.270479&amp;cid=CJLTWPH7S

[Saiedmomen]

@Rick Regan thanks!
@Adam Powell Please consider mentioning the expected idempotency in the docs.