3 ms·
It does, but the scala community is very familiar with the functional ("lambda") approach of leaving values in an optional context while transforming it. The i
by haimez 10y ago
It does, but the scala community is very familiar with the functional ("lambda") approach of leaving values in an optional context while transforming it.
The issue here stems from the existing community's culture, one especially full of trivially safe getters.
- neverminder 10y agoWell, maybe they need to learn the lesson the hard way, because when they start doing `foo.getBar().map(this::toString).orElse("Bar not found");` they will realize (hopefully) that this looks much more like Scala than classic Java.