Alejandro Serrano
Alejandro Serrano
> Will kotlin support these language features? I cannot say for sure, although I highly doubt that anything resembling type-level computation would make it into the language. The only exception...
This feature will appear as experimental in Kotlin 2.2.0. This PR will remain open for discussion for some time after the initial release, to gather any feedback.
There are two main reasons for not allowing them (yet): 1. Whatever the design, it should be uniform with nested type aliases. We don't want to end in a situation...
Since this feature is already released (nested type aliases are stable in 2.3.0, local ones are experimental), this KEEP discussion is being closed.
This seems indeed related to the change in Arrow 2.0 from a regular to a value class. Unfortunately, I don't see how we can fix this from Arrow -- changing...
Closed in favor of #393
I would rather prefer to have a DSL for the whole racing, if possible. This was just low-hanging fruit we could add to the library. I'll keep it open in...
@nomisRev what do you think about merging this, since it's a very small change requested by our users?
This is actually a problem with Dokka https://github.com/Kotlin/dokka/issues/3775, which hopefully is fixed soon (as it also affects the `kotlinx.coroutines` examples)
This issue is now fixed in Dokka, so examples should be correctly rendered now.