> If coroutines sometimes return single values and sometimes return multiple > values, it becomes much harder to write a generic async cache/memoization > system, because you can't indicate via the > type system that a single value > is expected.
There was never a proposal for coroutines to return different values. The whole debate revolves around the await() function. But it seems we’ve already decided what to do with it.
