I think it's actually a good move here, using a real language would invite too many comments getting caught in the weeds along the lines of: "actually the language does X, Y and Z to implement coroutines which this article skips over"
Agreed. My comment was more relating to the fact that comments about 'what' something is, aren't as helpful as answering the 'why', which you just did. =)
Mostly humor, but also a suggestion. Why? Because if it was real code I'd want the 'why' to be as specific as possible. It doesn't have to be a novel, but it also shouldn't be left open for interpretation.
Too many times have I gotten some ancient piece of code and cursed the author (sometimes this is even myself) for either not documenting it well or it had a bug or whatnot. "OMG, what were they thinking when they wrote this code?!" I never want to be in the position where someone is cursing me.
I tend to ignore comments in example programs because they look like this:
// Set x to 42
x += 42
It's a form of banner blindness.
By the way, first I felt a strong Pythonic vibe but then I realized that the colons after the statements were missing. I asked ChatGPT and it said Nim. I opened the Nim homepage and realized that Nim also uses the colons. Then it said it is probably just a form of pseudo-code, and it was right.
I reread the whole article to find the clue but never thought to read the commments. Really weird of me.
P.S. Did you see the mistake in the comment before you got here?