rfc:allow_null

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
rfc:allow_null [2022/02/07 16:55] – Add link to implementation craigfrancisrfc:allow_null [2022/02/08 14:43] – Add example changes craigfrancis
Line 62: Line 62:
 This also applies to those developers not using //strict_types=1//, which is excessive. This also applies to those developers not using //strict_types=1//, which is excessive.
  
-And while the individual changes are easy there are many of them, they are difficult to find, and often pointless (e.g. //urlencode(strval($name))//).+While individual changes are easythere are many of them, difficult to find, and often pointlesse.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://psalm.dev/docs/running_psalm/error_levels/|level 3]], with no baseline). 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://psalm.dev/docs/running_psalm/error_levels/|level 3]], with no baseline).
rfc/allow_null.txt · Last modified: 2022/04/05 17:49 by craigfrancis