I feel like you’ve latched onto something that is genuinely a non problem and if you get your way we all suffer reduced performance and a guarantee that a nil test is universally the same thing.
If you want an overridable nil test, write your own nil test like isNilish and make it mean what you like without disrupting the rest of the system. Problem solved and you’re not violating the open closed principle. Sent from my iPhone > On Mar 18, 2022, at 8:39 AM, s...@clipperadams.com wrote: > > > What you can do is turning it off globally in the setting (all compiler > option are listed there) > > But take care: we can not recompile the image without optimzations as this > adds intererrupt possibilities to code that was not interruptable before, > which breaks the code in for process switching itself, I think. > > So it sounds like my daydream that inlining be turned off by default is a > heavier lift than just flipping a switch, correct? > > In principle (ignoring the amount of work involved) what are your thoughts RE > my musing: “After 40+ years of Moore’s Law, can we turn off these inlines by > default?” and my hypothesis that this is an optimization that made sense at > the time but now adds complexity for questionable payoff?
