when using the synccontext, it seems the way it works is that context is captured when the task is scheduled, and brought back when the task will run
but akka seems to set the callcontext in other places outside of the scheduler
is this right? I may have to look at the code again
this is because of reentrancy.. if we only had the "suspend" behavior, that would be easy to solve the way you describe, but as we can multiplex many messages on the same actor, we need to re-set the context
as continuations are piped back as messages
found here... it's set in the actortaskscheduler only
to be honest. More and more im thinking that reentrancy mode should go away.