this Arrow-kt channel puts in a lot of effort, but also has a relatively large amount of conversation about bumping into limitations, and adapting to the the (kotlin|native|jvm|functional) tendencies when a blocker pops up. I see a lot of Arrow-kt introductions but apart from the programming Docs, I'm not sure if I've seen a clear metamodel that describes Arrow-kt definitions, or for that matter, where I am more concerned, how much of Arrow-kt is a compromise to remain Kotlin-compilable. it seems like Arrow is still relatively biased towards some JVM features but I don't yet get a sense if that's a forward assumption ongoing as well