Picking up a discussion from the last pull-request: How strictly do we want to avoid null? One way of doing things would be to always treat null as an error; so all optional things should be an Optional.
But some APIs might return null requiring us to constantly wrap things into Optional. Also, inside some class or method null is probably fine...
Picking up a discussion from the last pull-request: How strictly do we want to avoid
null? One way of doing things would be to always treatnullas an error; so all optional things should be anOptional. But some APIs might returnnullrequiring us to constantly wrap things intoOptional. Also, inside some class or methodnullis probably fine...