5 ms·

Arrow meta is a compiler extension that will bridge the gap even more e.g by bringing union types https://github.com/arrow-kt/arrow-meta https://github.com/arro

• valenterry 6y ago
  Unfortunately, the gap will stay huge due to the lack of capabilities the type-system, e.g. in higher kinded types and implicits. However, most people who choose Kotlin probably don't want to do "fully fledged" FP anyways and prefer to take the faster compile times etc. over it. I like the Scala side better though. ;)
  • WkndTriathlete 6y ago
    I'd argue that more day-to-day problems are solved with extremely usable record types (data class) than are solved with natively-supported HKTs.
    • valenterry 6y ago
      That's true, but a fallacy. Because HKTs prevent a certain class of problems from even coming to existence. What they predominantly do is help library author's to easily re-use and combine other libraries and provide them to their users while allowing for much greater flexibility than without them. So yeah, that's not a day-to-day problem of a system engineer (which I and most developers are) but they prevent a lot of these problems from even existing in the beginning. In the end, both are very useful in a different way and I don't like to work in languages that are missing either of them.