> C exported pretty much every abstraction of the underlying instruction set, but not coroutines.
My hunch is that the designers of C would have said "goto" and "switch" cover the use case where you have a bunch of peer chunks of code that you want to freely bounce between.
Remember, at the time function calls were considered expensive, so not support full coroutines across function call boundaries may not have been on their minds as much.
Indeed, and thanks for the excellent commentary on coroutines, awaiting the blog post. I think another fact played into their decision: coroutines do not specify how they are to be scheduled, that leaves room for arbitrary policies. Not that C shied away from keeping things undefined.
My hunch is that the designers of C would have said "goto" and "switch" cover the use case where you have a bunch of peer chunks of code that you want to freely bounce between.
Remember, at the time function calls were considered expensive, so not support full coroutines across function call boundaries may not have been on their minds as much.