Are workers as a concept planned for the stable release of coroutines, or coming later?

# coroutines

[danny]

Are workers as a concept planned for the stable release of coroutines, or coming later?

[danny]

i.e. not just constraining concurrency with a newFixedThreadPoolContext, but the actual number of coroutines total?

[nwh]

Can't you just keep track of the number of coroutines you launch? Or do I misunderstand your issue

[enleur]

you want to limit your coroutines or count them?

[danny]

Limit them - it's similar to Roman's KotlinConf presentation. In my case have I a connection pool and an external host I want to limit concurrency to. I want no more than that many workers running. There's an receive channel for keys to load, and an send channel for results - so those workers for loop in the receive channel

[danny]

Right now, I just for loop a range 1..numWorkers and launch(<http://Dispatchers.IO|Dispatchers.IO>) within the scope I need them to live for

[enleur]

isn’t enough for you?

[danny]

Sure, but sounded like there was a plan to support that as a pattern, I guess it's an actor?

[enleur]

https://github.com/Kotlin/kotlinx.coroutines/issues/172

[danny]

That's the guy! I'll watch that

[danny]

Cheers