I understand that channels as of today are marked ...
# coroutinesj
Jag
03/07/2019, 11:22 PMI understand that channels as of today are marked obsolete but I was looking to gain clarity on what the future of channels looks like (beyond what is described in issue #254). Could we still anticipate some form of a CSP like model -- facilitate communicating between coroutines? Are the proposed replacement of lazy async streams similar in concept to channels?
➕ 1
b
btilbrook-nextfaze
03/07/2019, 11:24 PMI’d love to hear an update on this as well!
j
Jonathan Walsh
03/08/2019, 1:00 AMcan you link to issue #254? I'm sure where to find it
r
r4zzz4k
03/08/2019, 1:08 AMHere you are: https://github.com/Kotlin/kotlinx.coroutines/issues/254
s
sitepodmatt
03/08/2019, 6:08 AMI don't think this means they are going to be obsolute, there are plenty of scenarios where the hot producer isn't applicable, or isn't a concern.
g
gildor
03/08/2019, 6:12 AMExisting API is obsolete, but it doesn’t mean that hot streams in coroutines are obsolete (or just plan to remove support of hot streams) in general
➕ 1
s
sitepodmatt
03/08/2019, 6:12 AMah okay, noted
e
elizarov
03/08/2019, 9:34 AMChannels are not obsolete. Channels are great communication primitive. They are not very good for data processing pipelines (think
filter { ... }.map { ... }p
Paul Woitaschek
03/08/2019, 10:50 AMWhat's the plans for the future on channels? Everything regarding channels is marked as obsolete and there seems to be no progress on it for months @elizarov
e
elizarov
03/08/2019, 11:07 AMOperators on channels are obsolete. Operators will work via cold-streams (for performance), but communication between coroutines will still happen via channel. They are even used internally in cold stream where you need to switch from one context to another.
👍 3
b
btilbrook-nextfaze
03/11/2019, 9:42 PMHow might we see a preview of cold streams? Is anything like that available?
e
elizarov
03/12/2019, 1:46 AMWait for it.
3 Views