8 karma · joined June 30, 2015
If you allow null as a return type you need to check for null if you want to use it or not. If you return Option[_] people e.g. just use map() on the return value and then map().map().map().map() on that etc. With Option your code usually does not care to check until the very last moment. Sorry my English is not good enough to make the point :-( And I know, saying "You need to use Option (and Applictives etc.) some years to grok" sounds arrogant and unsatisfactory. But I would not go back to a language without Option (and Applicatives etc.) usage in it's culture.
2. Sorry, wording is vaque, often deconstruction is
val MyValueObject(a,b,c) = myObject
I personally would listen instead of attacking me.
Option/Maybe solves the problem of things either being there or not (from databases, domain modelling, ...). As a side effect this solves NPEs.
Non-Nullable Types is there to solve (accessing non initialized variables) NPEs.
- Argued with the developers, they have not clue about Option/Maybe and what it's good for. They offer non-nullable type which solves just one - minor - problem with Null
- No deconstruction
- Their documentation in the beginning mixed features and planned features without discrimination. Spend a lot of time to find out trying to make them work that the features they've described in detail were fantasies.
- With deconstruction I would give it a try in a project.
To me it was much harder than firing people - hard by itself - because mass layed off people ask "why me" where I had no good answer.
Keep handkerchiefs around.
The F35 is not designed for dogfights but long range missle fights and stealth.