Spec#, nullables and more

[Gary Whatmore]

bearophile Wrote:

> Gary Whatmore:
> 
> > You're missing the point. The reason for seg faults is to terminate the application as quickly as possible. The developer then fires up the debugger and fixes the app. Seg faults should never happen in production code. You only release when all seg faults are fixed. The builtin unit tests in D can guarantee this with 100% test coverage.
> 
> Unittests help remove and avoid some bugs, but experience shows they don't solve/avoid all problems. Null exceptions do happen in production code. 100% coverage of unittests can't avoid all possible bugs, because it's easy to miss some code paths in unittests. Take a look at bugzilla to see many basic bugs in Phobos despite the usage of unittests.

Doesn't it mean that instead of complicating the language we write more unit tests? Surely the stream of new bugs ends at some point. Then we are production ready. Just look how look it took to stabilize C++. 30+ years is acceptable for D. C++ didn't have test driven development knowledge, we have.