It'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.)
That's why Rust's safety first creed is so welcome. (And that there's --strict in TypeScript.)
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.