https://kotlinlang.org logo
#arrow-contributors
Title
# arrow-contributors
s

stojan

09/19/2020, 9:33 AM
I created the module and moved
Option
there. At first I made
arrow-option
depend on
arrow-core-data
(
Option
need
Show
,
Predicate
,
Either
and a few other utilities from core-data). However arrow-core-data also needs
Option
.
MonadLogic
,
Monoidal
,
Semigroup
,
Travers
etc... use it internally or in a public API. Since
Option
was marked for deprecation, I assume removing the
Option
usages from arrow-core-data is the way to go, right?
Semigroup
uses
Option
internally, this can be replaced with nullable types without altering the public API
FunctorFilter
uses
Option
as part of the public API....
fun <A, B> Kind<F, A>.filterMap(f: (A) -> Option<B>): Kind<F, B>
do I also replace this with nullable types? (that would change the public API without deprecation cycle)
r

raulraja

09/19/2020, 7:45 PM
Makes sense, yeap that should be good, thanks Stojan!
For FunctorFilter I think it's fine since it has been released deprecated already without an alternative 😞
Also we may want to consider rename to mapNotNull.