rfc:allow_null
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:allow_null [2022/01/21 00:02] – craigfrancis | rfc:allow_null [2022/02/08 14:43] – Add example changes craigfrancis | ||
---|---|---|---|
Line 62: | Line 62: | ||
This also applies to those developers not using // | This also applies to those developers not using // | ||
- | And while the individual changes are easy - there are many of them, they are difficult to find, and often pointless | + | While individual changes are easy, there are many of them, difficult to find, and often pointless, e.g. |
+ | |||
+ | * urlencode(strval($name)); | ||
+ | * urlencode((string) $name); | ||
+ | * urlencode($name ?? '' | ||
Without the changes below, developers will need to either - use these deprecation notices, or use very strict Static Analysis (one that can determine when a variable can be //NULL//; e.g. Psalm at [[https:// | Without the changes below, developers will need to either - use these deprecation notices, or use very strict Static Analysis (one that can determine when a variable can be //NULL//; e.g. Psalm at [[https:// | ||
Line 133: | Line 137: | ||
===== Implementation ===== | ===== Implementation ===== | ||
- | TODO | + | https:// |
+ | |||
+ | This patch currently defines // | ||
+ | |||
+ | It works a bit like // | ||
+ | |||
+ | It's a fairly easy drop in replacement for // | ||
===== Rejected Features ===== | ===== Rejected Features ===== |
rfc/allow_null.txt · Last modified: 2022/04/05 17:49 by craigfrancis