Re: [RFC] Deprecate passing null to non-nullable arguments of internal functions

While making internal functions treat non-nullable types consistently with userland is an absolute win, I do wonder if it should be done simultaneously with changing some functions to formally accept nulls. I'm thinking back to all the pain caused when *count() *starting raising a warning for null values. We saw a lot of code that passed undeclared variables to *count()* and I can imagine people writing similar code with something like *strlen()*