Am Thu, 27 Jul 2017 17:59:41 +0000 schrieb Adrian Matoga <[email protected]>:
> On Thursday, 27 July 2017 at 17:43:17 UTC, H. S. Teoh wrote: > > On Thu, Jul 27, 2017 at 05:33:22PM +0000, Adrian Matoga via > > Digitalmars-d wrote: [...] > >> Why can't we just make the compiler insert null checks in > >> @safe code? > > > > Because not inserting null checks is a sacred cow we inherited > > from the C/C++ days of POOP (premature optimization oriented > > programming), and we are loathe to slaughter it. :-P We > > should seriously take some measurements of this in a large D > > project to determine whether or not inserting null checks > > actually makes a significant difference in performance. > > That's exactly what I thought. A typical non-synthetic worst case candidate should be in the tests that would invoke a lot of null checks. (Could be a function call at first to count checks per run of executable and pick a good project.) -- Marco
