@WalterBright This hack doesn't change a single damn thing for the majority of performance-minded users anyway. We are not in any rush. Code goes in and stays there for months, many things wait 'that tiny speed up' for half a year no problem at all.

Let's take a step back and do the right thing for a change. Open a parallel discussion on froce_inline/no_inline. Not going to accuse you but  dodging this question for quite some time arguing that compiler knowns better what to inline and then *BAH*:
 "here this tiny hack, it prevents inlining in my compiler"
... cause you *sometimes* indeed know better what to inline then the compiler.