doing it blocking is trivial but if you reentrantly call int

Question

doing it blocking is trivial but if you reentrantly call into the main thread as you saw with runBlocking it never completes

aballano · Answer

would it work by changing this <https github com arrow kt arrow blob master modules effects arrow effects data src main kotlin arrow effects typeclasses suspended FxSyntax kt L50> to something like ``` fun lt A gt CoroutineContext effect continueOn CoroutineContext = EmptyCoroutineContext f suspend gt A Kind lt F A gt = asyncOp defer this effect f effect continueOn continueOn ``` I mean I just tried on arrow but got an error xD

aballano · Answer

``` Cause Cannot serialize error type ERROR Unknown type parameter 1 File being compiled at position file Users aballano workspace arrow modules effects arrow effects data src main kotlin arrow effects typeclasses ConcurrentCancellableContinuations kt The root cause was thrown at SerializerExtension kt 83 ```

pakoito · Answer

clean rebuild

aballano · Answer

shall I create a PR and continue the discussion there

aballano · Answer

or doesn t make sense to go this way

aballano · Answer

this change would basically allow this <https kotlinlang slack com archives C8UK6RTHU p1554465378024800>

pakoito · Answer

there are a couple of potential complications with that approach because we d be clearing the CoroutineContext

pakoito · Answer

the design of the thing requires that to override the Dispatcher you need the pre existing context

pakoito · Answer

and smash it together

pakoito · Answer

this is a problem through the library

aballano · Answer

so this means it might be improved right That s even better since this right now would essentially be saving the implementation client to manually `continueOn UI ` after doing the effect anyway no So worst case scenario we save the client one line ok hand and best we even improve over what they would do manually otherwise +1

aballano · Answer

or would that ` continueOn EmptyCoroutineContext ` break something for the caller in case they don t specify the `CoroutineContext` In such case we could just if else and not call `continueOn` at all thinking face

aballano · Answer

``` fun lt A gt CoroutineContext effect continueOn CoroutineContext = EmptyCoroutineContext f suspend gt A Kind lt F A gt = asyncOp defer this effect f effect apply if continueOn = EmptyCoroutineContext continueOn continueOn ```

pakoito · Answer

I suggest adding a new API instead of modifying this one and matching on type

pakoito · Answer

effectAndReturn or something like that

pakoito · Answer

that way the additional parameter is unmissable and the API name specifies what it does

aballano · Answer