3 ms·
Given the semantics of coroutines, what would you consider a sane call stack? Should each routine have its own stack? This is not a glib question, I genuinely
by gumby 9y ago
Given the semantics of coroutines, what would you consider a sane call stack? Should each routine have its own stack?
This is not a glib question, I genuinely don't know what the proper answer might be. Perhaps what's needed is a different debugger mechanism?
- spc476 9y agoMy own implementation of coroutines for C [1] requires each coroutine to have its own stack. It simplifies things quite a bit. [1] https://github.com/spc476/C-Coroutines https://github.com/spc476/C-Coroutines [2] [2] More of a "proof-of-concept" than something really meant for production.