On Friday, 17 November 2017 at 06:32:03 UTC, codephantom wrote:
On Friday, 17 November 2017 at 05:50:24 UTC, rumbu wrote:
You are not ending with nothing, you are ending with a run
time error in D. In C# it's a compile-time error. Ideally,
something ending for sure in an error at run time, must be
catch at compile-time.
Well.. sometimes it's just nice...to do nothing, and I'm glad D
lets me do that.
And the runtime should just stay out of it. It's always
interfering in something - even when its nothing.
I don't even imagine how the runtime can stay out of
dereferencing a null pointer.
I know your aversion towards C#, but this not about C#, it's
about safety. And safety is one of the D taglines.
