3 ms·
I'm doubling down on my "both worlds" point, whether you state it as (scala = FP and OO) or (scala = FP or OO). My choice to be null-free does not survive my c
by mrkeen 7y ago
I'm doubling down on my "both worlds" point, whether you state it as (scala = FP and OO) or (scala = FP or OO).
My choice to be null-free does not survive my coworkers' choice to use null. Likewise with mutability, purity, inheritance etc.
The feature that I want is to look at (n : T) and understand that T is T, not (T | ? extends T) and that n is n, not (n | null), or n now and n' later.
- pas 7y agoIt's not Scala's fault if a team can't decide on a coherent coding style/standard, but I feel your point :( That's why Rust's safety first creed is so welcome. (And that there's --strict in TypeScript.)