>- "A coroutine is like a control construct"---a coroutine is a control construct. There is no "like".
Pedantic. A coroutine is a control construct in the same way an Exception is a control construct, or in the way a tomato or a cucumber is a fruit.
Adopting a particular naming depends on the categorization and the intention, not merely on the capabilities of a construct.
Even more so in a post, were the notion needs to be introduced to people who only associate the concept of a "control construct" to the more explicit and tamer constructs referred to as such, if and for loops, goto, etc.
>- "But coroutine is also like a variable"---a coroutine closes over an environment. I.e. it is a closure. This doesn't really have much to do with being "like a variable". Representing closures is well studied in programming language research and there are many techniques for handling it E.g. http://matt.might.net/articles/closure-conversion/*
The first part is just a formal definition, which doesn't negate the statement, and the latter part is just a generic reference to research on closures.
One could use the same kind of saying-nothing responses to all kinds of posts or papers.
"One could use the same kind of saying-nothing responses to all kinds of posts or papers."
You misunderstand.
If you know the name of the concept you can search for more information.
If you read the section on "But a coroutine is also like a variable" you'll see the author is struggling with how to represent coroutines. Closure conversion deals with representation.
Pedantic. A coroutine is a control construct in the same way an Exception is a control construct, or in the way a tomato or a cucumber is a fruit.
Adopting a particular naming depends on the categorization and the intention, not merely on the capabilities of a construct.
Even more so in a post, were the notion needs to be introduced to people who only associate the concept of a "control construct" to the more explicit and tamer constructs referred to as such, if and for loops, goto, etc.
>- "But coroutine is also like a variable"---a coroutine closes over an environment. I.e. it is a closure. This doesn't really have much to do with being "like a variable". Representing closures is well studied in programming language research and there are many techniques for handling it E.g. http://matt.might.net/articles/closure-conversion/*
The first part is just a formal definition, which doesn't negate the statement, and the latter part is just a generic reference to research on closures.
One could use the same kind of saying-nothing responses to all kinds of posts or papers.