going back to stackful vs stackless coroutines, fr...

# coroutines

[groostav]

going back to stackful vs stackless coroutines, from a debugging perspective, can we implement some kind of object: CustomException(){ override fun fillStackTrace based scheme to keep the stack context many-state-machine-switches in?