You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Android Activities, Fragments, and Views there is a getContext() method that is used frequently. When used with Kotlin the IDE suggests using property access syntax with the synthetic property context. This is shadowed when using an async or launch coroutine block, though, by the CoroutineContext context of CoroutineScope.
We can use getContext() instead and it's not the end of the world, but I wanted to file the issue to see if there should instead be an alternate name for the CoroutineContext. I imagine many people will run into this "issue" whether writing code or reading other's code and getting confused by the two different "contexts".
Cheers.
The text was updated successfully, but these errors were encountered:
In Android Activities, Fragments, and Views there is a
getContext()
method that is used frequently. When used with Kotlin the IDE suggests using property access syntax with the synthetic propertycontext
. This is shadowed when using anasync
orlaunch
coroutine block, though, by the CoroutineContextcontext
of CoroutineScope.We can use
getContext()
instead and it's not the end of the world, but I wanted to file the issue to see if there should instead be an alternate name for the CoroutineContext. I imagine many people will run into this "issue" whether writing code or reading other's code and getting confused by the two different "contexts".Cheers.
The text was updated successfully, but these errors were encountered: