I can't reproduce this: https://3v4l.org/9NvcY

it was triggered by a fuzzy-testsuite on two out of millions of calls :-(

i replaced the offending code path with a construct used all over the codebase which should silence it as intended 

i find it interesting that it's even possible that this warning triggers at all when "Null Coalescing Operator" is used because there is no point to look at the array offset when the whole $arr is NULL

-  $arr = mysqli_fetch_row($db->query($sql));
-  $oldcontent = $arr[0] ?? '';
+  $oldcontent = (string)(mysqli_fetch_row($db->query($sql))[0] ?? '');

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.

Opening, since feedback had been provided.

Unless there's some working reproduction code for this, I don't think we can do anything here.

Hi, here is a way to reproduce the issue:

https://3v4l.org/mX3Pf

sadly "echo strval($arr['foo']) ?? 'bar';" is a invalid reproducer and expected to thow a warning becaus ein that line strval() is feeded with $arr['foo'] and "?? 'bar'" would only be relevant wehn that returns NULL which is not possible by the nature of strval()

this is a completly different beast
$oldcontent = $arr[0] ?? '';

@kevin-anidjar: That does not reproduce the issue. The code must use ?? immediately after a value and without that value going through a function.

@requinix@php.net: in previous PHP versions, this code did not throw an error and the returned value was instead considered as null.

> in previous PHP versions, this code did not throw an error 
> and the returned value was instead considered as null

but your code is *expected* to throw an error in newer versions while "$arr[0] ?? ''" is not, no matter if $arr or $arr[0] is undefined

My bad, did not see this in the changelog:

Array-style access of non-arrays

Trying to use values of type null, bool, int, float or resource as an array (such as $null["key"]) will now generate a notice.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.