Hacker News new | ask | show | jobs
by PaulDavisThe1st 2014 days ago
> Checking for null at higher levels is a bad habit from C.

or its a way to allow the developer to decide how much they are willing to pay for checking, since the library doesn't do it itself.

I appreciate the sentiment that the ability to not check has caused many problems; I also appreciate using APIs that don't cost me conditionals when I know that the passed in value cannot be null.

Sometimes I get the sense that Rust tries to be a language that promises you can get the best of all worlds here, but everytime I did deeper, it seems that this is an illusion.