Hacker News new | ask | show | jobs
by bananas 4413 days ago
Yep but you'd know which dereference it was if you unrolled it. Nulls happen unfortunately even with the best checking and intents.
1 comments

Nulls happen, that's why you use the best checking. It's not the best checking if you get thrown NullReferenceExceptions
Definitely but that gurantee is thrown away the moment you pull a 3rd party black box in.

I'm suggesting it's feasible but not necessarily perfect and when it does go boom, which it does when you have 100 million HTTP hits a day, you need to be able to find out precisely where it went wrong. LINQ makes that damn hard:

   NullReferenceException
   Company.Product.Assembly.Namespace.Type.Method() +14
   ...
When line 14 has 22 dereferences then you have no idea why it broke.