Posted Aug 31, 2012 9:58 UTC (Fri) by cras (guest, #7000)
Parent article: Quotes of the week
I can't believe no one mentioned the reason this __always_inline vs. inline business happened in the first place (according to my guesses - if I'm completely wrong feel free to correct :). If you want to put functions into header files, they need to have "inline" keyword or you'll get a warning:
foo.h:1:12: warning: ‘foo’ defined but not used [-Wunused-function]
So now people are adding inline keywords to functions simply to avoid this warning, even for functions where inlining might not be optimal. It makes perfect sense for the compiler to start ignoring the inline keyword in these situations.