| > not all structures have a sane default for all not optional, nilable parameters. What is the default underlying reader for a bufio.Reader? I think you're actually agreeing with nemothekid here, what you're saying is that there is no sensible default value for a bufio.Reader. In Rust terminology, that would mean bufio.Reader would not implement the Default trait. Types need to explicitly implement the Default trait, so only types where that makes sense implement it. > I simply do not have a problem programming with nil-able types Yes, that's going to make a big difference to how you feel about features that reduce the chance of errors like that. I'd hazard a guess that in C# the most common exception that is thrown is the NullReferenceException, after a quick search[1] it looks like NullPointerException is a good bet for the most common exception in Java. Most of those IlligalArgumentExceptions are probably from null checks too. > Fundamentally, I do not want to spend hours of my life dealing with safeguards which are protecting me from a few minutes of debugging. Similarly, I've already spent hours of my live dealing with null and undefined value errors, and I'd like to stop doing that. So I welcome new languages and new language features that help to stop those errors before they happen. [1] https://blog.overops.com/the-top-10-exceptions-types-in-prod... |