Is there any explanation?
# coroutinesm
marcinmoskala
10/12/2018, 10:36 AMIs there any explanation?
e
elizarov
10/12/2018, 10:37 AMvar prime: Intelizarov
10/12/2018, 10:37 AMI’ve hit the same ~1.5 years ago when prototyping channels for Kotlin.
elizarov
10/12/2018, 10:38 AMFiled this one back then: https://youtrack.jetbrains.com/issue/KT-15514
elizarov
10/12/2018, 10:38 AM(2 years ago, oh my!)
m
marcinmoskala
10/12/2018, 11:22 AMI guessed that it is because of problems with capturing by lambda. Should I add it as an error or someone else already done it? This is build-in Kotlin problem so I think that issue tracker is the place.
marcinmoskala
10/12/2018, 4:55 PMi
ilya.gorbunov
10/14/2018, 3:29 PMBut is this related to suspending functions?
I mean the problem is that a mutable variable is captured in
filtere
elizarov
10/14/2018, 6:45 PMYes. That is exactly the issue I’ve filed. In general, capturing mutable variable into a lambda that is executed “not in place” should be at least a warning. There are cases where it is Ok, though. It would be hard to distinguish them.
m
marcinmoskala
10/14/2018, 9:02 PM😱 I see it now. @antonkeks This is even better puzzler!
i
ilya.gorbunov
10/15/2018, 4:45 PMA simplified puzzler on this subject was already presented on the latest KotlinConf:
https://github.com/angryziber/kotlin-puzzlers/blob/master/src/functions/closeCapture/CloseCapture.kts
5 Views