Is this not fixed <https youtrack jetbrains com issue KTIJ 1 kotlinlang #coroutines

Channels

100daysofcode

100daysofkotlin

100daysofkotlin-2021

androidgithubprojects

cincinnati-user-group

competitive-programming

event21-community-content

java-to-kotlin-refactoring

jvm-ir-backend-feedback

kotlin-multiplatform-contest

kotlinultimatechallenge

myndocs-oauth2-server

naming

navigation-architecture-component

practical-functional-programming

proguard

prozis-android-backup

refactoring-to-kotlin

russian-kotlinasfirst

skia-wasm-interop-temp

stayhungrystayfoolish

swagger-gradle-codegen

tricity-kotlin-user-group

Title

Sourabh Rawat

03/03/2022, 4:29 AM

Is this not fixed? https://youtrack.jetbrains.com/issue/KTIJ-18630 Can't access

reservation

parameter in debugger at the debug point at line 26. It says

This variable is inaccessible because it isn't used after the last suspension point

Using coroutines

1.6.0

ephemient

03/03/2022, 6:20 AM

it's fixed in that the IDE tells you why the variable isn't available

there's a separate issue for changing how coroutines are compiled to make such variables available, https://youtrack.jetbrains.com/issue/KT-48678

Sourabh Rawat

03/03/2022, 6:23 AM

Ah that is what I am exactly facing. Thanks a lot for sharing.

ephemient

03/03/2022, 6:23 AM

but FYI, even plain old (non-coroutine) Java code allows variables to be garbage-collected before the end of the scope if they aren't referenced by later statements: https://shipilev.net/jvm/anatomy-quarks/8-local-var-reachability/

of course that's a lot less likely to happen than the case where the coroutine state machine simply optimizes the variable out, but if coroutines were to keep them, they'd be stricter than plain old code

113 Views

#coroutines Join Slack