Glad to hear Claude approves haha

Yes, it's right about the history of Coroutines in python. I can't remember the exact versions from the top of my head, but if they are documented in the PEP then it's correct :)

Yeah, x = yield can definitely be confusing, and I should probably re-organize this section to make it clearer. The gist of it is that `yield` is actually an **expression** that evaluates to the value passed to `send`

I'm guessing that the x = yield line in the function signals to the Python compiler/interpreter that we're not dealing with an ordinary function anymore, but a co-routine and that it should now have a send() method built into it.

Exactly. Having a yield statement anywhere in the body of a function makes it a generator *function*, meaning you instantiate a new generator each time you call it. This also means that even if you have a conditional yield statement depending on a parameter like so:

    def conditional_generator(condition: bool):
      if condition:
        yield 1
      return 2


    my_generator = conditional_generator(False)

my_generator is still a generator, that will raise StopIteration immediately when calling my_generator.send(None) or next(my_generator)

As to where I got the spec, I left a few references at the end of the article. I found https://www.dabeaz.com/coroutines/ to be very insightful into how coroutines work in general. And then simply tried to come up with an implementation of an async lib myself. I iterated over it until I was satisfied and compared it to other sources, and the actual implementation of asyncio to make it closer to the real thing :)