A modern programming language that makes developers happier.

kotlinlang

Screenshot 2025-04-19 at 07.16.42.png

Add:
```context(logger: Logger) fun log() = logger.log()```

Bit off topic; I’ve been programming Kotlin for 3 years now and never used this feature (context receivers). Is it kind of a niche feature? Or am I missing out on something good?

It's very new and still in development, so for now you should avoid using it unless you really need to
But for creating contextual/complex DSLs that's very great

Experimenting with them is absolutely worth it.

I'm still not convinced by the bridge functions :confused:

<@UFGCACPE0> I've found them helpful if a type has "too many things exposed" and thus would pollute the scope if brought in as a receiver. That type may still be valid as a normal receiver because it's difficult with normal receivers to have too many in scope (each receiver necessarily results in one extra level of indentation), but it's really easy with contexts

Isn't it getting <https://blog.jetbrains.com/kotlin/2025/04/update-on-context-parameters/|deprecated in 2.3?>

No Context Parameters and Context Receivers are a different thing

Screenshot 2025-04-30 at 07.49.24.png

I understand that in the final version of the context parameters, this won't be an error, right?
If not, I don't understand why they were created.

You have to name the parameters, ex: `context(thing: String)`, then you'll be able to use it as `thing.something()`

Sorry, I think I understand how it works.
Since I'm used to using context receivers, I thought that "_:" was going to be the same as an Extension Function.