Actors only have input channels. I’m guessing it is that way because, in pure actor-oriented programming, the concept of an “output channel” doesn’t really make sense because all actors only communicate by
sending messages to other actors. That said, I doubt most people actually use
actor
for pure actor-y programming in Kotlin, and I agree it would make sense to have a builder that combines
actor
and
produce
(I have a use case for this too).