I am personally surprised by the heavy use of Option, but I've recently also encountered some issues due to nested null
in generic code 😅 It even resulted in me making 2 bug fixes against them in Quiver. I'm looking forward to working together with the Quiver team to facilitate all usages, so that we can solve everyones needs together for FP in Kotlin. To that end I'd love to get feedback on my questions, and remarks in the PR shared by @Hugo
Also, we plan to release 1.2.0-RC at the end of this week with the final deprecations to 2.0.0. It will be more clear in the deprecation message, and in the release post but I am inviting all of you already to check it out (or do so on an alpha versions) and let us know if any of the APIs critical to you are being deprecated. So we can consider moving them to Quiver, or can keep/move them in Arrow-core if the community consider them core
to fp in kotlin_._ The release post wil also explain the rationale
of why some APIs are being deprecated. We care about the success of functional programming in Kotlin, and is also why we kept
around when it was originally marked for deprecation pre-1.0.0. (Thanks to a discussion started by @mitch
at the time🙏).
Thanks in advance all for your support of Arrow and FP in Kotlin ❤️ :kotlin-intensifies-purple: :arrow-intensifies: