Destructuring assignment from null does not raise warning #3640
Labels
bug
Documentation contains incorrect information
Comments
|
Well, let's say it's a feature, but document it (also for |
tgr
added a commit
to tgr/doc-en
that referenced
this issue
Aug 24, 2024
tgr
added a commit
to tgr/doc-en
that referenced
this issue
Aug 24, 2024
Update notes about the handling of missing keys and non-arrays during array destructuring to match the behavior seen on 3v4l.org, which doesn't issue a warning or notice in some cases where the documentation claims it does. Also update list() docs to provide the same information. list(): * missing key: https://3v4l.org/bYBt6 * destructuring an integer: https://3v4l.org/7lNhK * a boolean: https://3v4l.org/p5LDd * a string: https://3v4l.org/KHSAH * null: https://3v4l.org/lk1iu array notation: * missing key: https://3v4l.org/KCiTC * destructuring an integer: https://3v4l.org/louVG * a boolean: https://3v4l.org/SWL5L * a string: https://3v4l.org/aK90L * null: https://3v4l.org/Y8cOY Fixes php#3640.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://www.php.net/manual/en/language.types.array.php#language.types.array.syntax.destructuring says
but this isn't actually true when assigning null;
[$x, $y] = null;does not raise a notice or warning (eval). Same goes for destructuring with an associative array (eval). This seems to be specific to null (e.g.[$x, $y] = [];raises a warning: eval) and to destructuring assignment (e.g.null[0]raises a warning: eval).Not sure if this is a bug or a documentation issue, but either there should be a warning or this special case should be documented.
The text was updated successfully, but these errors were encountered: