Replies: 3 comments 3 replies
-
@dalewking I think it is historical sample, I don't see a reason to use LaunchedEffect now, I'll patch the docs |
Beta Was this translation helpful? Give feedback.
0 replies
-
That's what I thought. To be clear though using a remember is still
important so that you have the same instance across recompositions.
Dale King
…On Mon, Aug 18, 2025, 3:30 AM Alexander Sysoev ***@***.***> wrote:
@dalewking <https://github.com/dalewking> I think it is historical
sample, I don't see a reason to use LaunchedEffect now, I'll patch the docs
—
Reply to this email directly, view it on GitHub
<#451 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACUPTVQ2CPQIGPF4GJ3F7D3OF6IHAVCNFSM6AAAAACED4QFDCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMJTG42TKOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
3 replies
-
Addressed in #455 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In the example here:https://github.com/Kotlin/kotlinx-rpc/blob/main/samples/ktor-all-platforms-app/composeApp/src/commonMain/kotlin/App.kt#L38
I see lots of code for using LaunchedEffect, but I'm not sure the point of the LaunchedEffect in this case. LaunchedEffect is for launching coroutine code but there is nothing in there that is suspending. And withService never returns null.
Is there some reason that this is not good enough (note I extracted the client into a client variable):
Beta Was this translation helpful? Give feedback.
All reactions