Is there any publicly-available information about ...
# language-evolution
y
Is there any publicly-available information about
coeffects
? Because I heard that there's some internal discussions about it and the name itself sounds intriguing especially because it'll allegedly solve DI. Obviously it's in a very very very early stage, but if there's a keep or something for it so that the community can discuss it then that'd be quite hlepful
e
TL;DR: It is the same as multiple receivers.
Tomas Petricek has a nice site with an overview of (unchecked) coeffects. Totally non-Kotlin related (we plan them to be integration into function types), but the concept is explained quite well: http://tomasp.net/coeffects/
y
So, from what I understood from that, it is basically extra machinery that will presumably be provided on top of multiple receivers (in the stdlib probably) to make the usage of the concept of coeffects easier. Am I correct in my understanding or is it going to be something more complex like
suspend
? Side note but I admire the fact that the Kotlin team looks around in academia to find elegant solutions like
suspend
(with its CSP) and now
coeffects
e
Multiple receivers are coeffects. No extra machinery is needed.
🙏 1
y
Oh okay that makes sense I think I got confused because the tweet that mentioned coeffects said that it's built on top of multiple receivers. Thank you!