Hello! I asked this over in <#C0B8MA7FA|getting-started> and it was suggsted that ask ask over here...

# coroutines

[Brian Carr]

Hello! I asked this over in #getting-started and it was suggsted that ask ask over here.

[mng]

1. Maybe i'm misunderstanding but a suspend function can only ultimately be called using a CoroutineScope from a function that is not suspend

[Brian Carr]

I think as of the release of 1.4.3, my question might be irrelevant. I’m writing tests to confirm right now. However, my base problem was that I had ThreadLocal storage being accessed as coroutineContext elements. I had a safeGet method which checked if the key was in the context before calling get() on the ThreadLocal. My goal was to try to prevent calls to ThreadLocal.get() from inside a coroutineScope

[Brian Carr]

it’s still bad to call ThreadLocal.get() if no parent scope/context has had the contextElement added, but it’s less risky than it was before today’s release.

[Brian Carr]

though it appears that ThreadLocal.remove() behaves the same way as ThreadLocal.set() does with today’s release.