A modern programming language that makes developers happier.

kotlinlang

:android-wave: If I create an @optics for a model that has a `someField: String?` , in order to set/modify it I have both `someField` and `nullableSomeField` lenses. This won't be a case in Arrow 2.0? If not, why are both lenses are created instead of only the `nullable` one?

right now @optics give you a single `someField: Optional&lt;T, String&gt;`, but with Arrow 2.0 you'll get `someField: Lens&lt;T, String?&gt;`

the difference is that with the 1.x behavior you cannot change a `null` value into a non-`null` one and viceversa, but with 2.x behavior you can

image.png

hmm weird, I can see only that in the generated code, using Arrow 1.2.4