Re: NULL Coercion Consistency
| From: | Craig Francis | Date: | Mon, 23 May 2022 18:45:48 +0000 |
| Subject: | Re: NULL Coercion Consistency | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117773@lists.php.net to get a copy of this message | ||
On 8 Apr 2022, at 18:34, Craig Francis <craig@craigfrancis.co.uk> wrote:
> I've written a new draft RFC to address the NULL coercion problems:
> https://wiki.php.net/rfc/null_coercion_consistency
> <https://wiki.php.net/rfc/null_coercion_consistency>
For those against my RFC, can you take a quick look at this patch for Laravel:
https://github.com/laravel/framework/pull/36262/files#diff-15b0a3e2eb2d683222d19dfacc04c616a3db4e3d3b3517e96e196ccbf838f59eR118
<https://github.com/laravel/framework/pull/36262/files#diff-15b0a3e2eb2d683222d19dfacc04c616a3db4e3d3b3517e96e196ccbf838f59eR118>
If passing NULL to
htmlspecialchars() represents a problem, as used in templates like
<p>Hi {{ $name }}</p>, presumably this patch should be reverted?
Craig