A modern programming language that makes developers happier.

kotlinlang

> ```Experimental context receivers are deprecated and will be superseded by context parameters. Please don't use context receivers. You can either pass parameters explicitly or use members with extensions.  
> 
> See new context parameters proposal: <https://github.com/Kotlin/KEEP/blob/context-parameters/proposals/context-parameters.md>. During the transition period, neither context receivers nor context parameters will be supported. This warning will become an error in future releases.```
As a quick straw poll, how are most of us `context-receivers` lovers expecting to handle the migration?
:one: go full ostrich, ignore it, stick to the last kotlin version that supports `context-receivers` and hope we can wait out the kotlin release that enables `context-parameters`
:two: stop using `context-receivers` for the time being, revert to `.bind()` et al, or where possible use `Raise<E>` as an extension receiver
:sob: find a corner and cry until it all blows over

Added an additional cry emoji because that’s what I’ll be doing.

I'm just going to assume :sob: is the same as  :one:  just with additional tears

It was said here that there won’t be a gap between context receivers and context parameters? <https://youtrack.jetbrains.com/issue/KT-8087/Make-it-possible-to-suppress-warnings-globally-in-compiler-via-command-line-option#focus=Comments-27-10137847.0-0|https://youtrack.jetbrains.com/issue/KT-8087/Make-it-possible-to-suppress-warnings-globally-in-compiler-via-command-line-option#focus=Comments-27-10137847.0-0>

damn, wasn't that a kotlin feature the newer versions of arrow was kind of relying and counting on? sorry late to the party but if someone could give an eli5/tldr that would be sweet

Internally, Arrow :arrow: doesn’t use context receivers. Btw, context parameters are context receivers under steroids. It’ll not change too much