I just saw Option is deprecated as it is promoting...
# arrowd
dephinera
10/15/2020, 8:51 PMI just saw Option is deprecated as it is promoting bad coding style. However I'm curious are there really more downsides than upsides to make that decision. What's the experience with it? It was very useful for filterMap (what will the alternative be in this case?) and when using RxJava, where nu values are not allowed
s
streetsofboston
10/15/2020, 9:02 PMFor filterMap, you could use mapNotNull instead, correct?
d
dephinera
10/15/2020, 9:05 PMNot exactly, as filterMap lets you to map the values you want by returning some(myNewValue) and filter away the others for which you return none()
dephinera
10/15/2020, 9:05 PMAh, I get your point... 😃
s
streetsofboston
10/15/2020, 9:07 PMBut yes, the RxJava issue remains. You’d have to create your own ‘wrapper’.
They tried so solve some issue about Java not being having a null-safe type system… still, this decision caused more issues than it solved, in my opinion. Kotlin’s `Flow`s don’t have that issue… they can just emit null values.
k
kioba
10/15/2020, 9:28 PMOption will be moved into a separate library you cans till use it with RxJava.
👍 1
☝️ 4
g
georg
10/17/2020, 6:51 PMYou could create a typealias for
Either<Unit, T>d
dephinera
10/17/2020, 7:10 PMYeah, that's not a bad idea actually
5 Views