Re: [PHP-DEV] Nullsafe array access can still emit a warning
I completely agree with Marco. We should not mix up nullsafe operator with array access. As for me, aforementioned code works as expected. As an improvement, we can think of access-safe operator (like `$arr[?0]`), however I'm not sure if introduction of such will make sense. Regards Yevhen On Wed, Aug 24, 2022, 4:11 PM Marco Pivetta wrote: > Hey Gert, > > On Wed, 24 Aug 2022 at 14:59, Gert de Pagter wrote: > > > Hi Internals, > > > > I recently learned that using null safe on an array access can still > > emit a warning when the array access is not defined. I kinda expected > > it to work like a null coalesce and just short circuit there,without > > the warning. > > > > Is there any chance this behaviour could be changed in a n upcoming > > PHP version? I didn't see anything mentioned specifically about this > > in the RFC. > > > > https://3v4l.org/1raa8 > > > > Greetings, > > Gert de Pagter/ BackEndTea > > > > This seems expected behavior to me: it's "nullsafe", not "undefinedsafe". > > If it operated like `??`, then `$undefined?->bar()` would be valid too, > which seems wrong, IMO. > > Marco Pivetta > > https://twitter.com/Ocramius > > https://ocramius.github.io/ >
Re: [PHP-DEV] Nullsafe array access can still emit a warning
`$undefined?->bar()` does feel wrong, but `$arr[0]?->bar()` does not to me. But maybe i've just been using javascript too much lately On Wed, 24 Aug 2022 at 15:11, Marco Pivetta wrote: > > Hey Gert, > > On Wed, 24 Aug 2022 at 14:59, Gert de Pagter wrote: >> >> Hi Internals, >> >> I recently learned that using null safe on an array access can still >> emit a warning when the array access is not defined. I kinda expected >> it to work like a null coalesce and just short circuit there,without >> the warning. >> >> Is there any chance this behaviour could be changed in a n upcoming >> PHP version? I didn't see anything mentioned specifically about this >> in the RFC. >> >> https://3v4l.org/1raa8 >> >> Greetings, >> Gert de Pagter/ BackEndTea > > > This seems expected behavior to me: it's "nullsafe", not "undefinedsafe". > > If it operated like `??`, then `$undefined?->bar()` would be valid too, which > seems wrong, IMO. > > Marco Pivetta > > https://twitter.com/Ocramius > > https://ocramius.github.io/ > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
Re: [PHP-DEV] Nullsafe array access can still emit a warning
Hey Gert, On Wed, 24 Aug 2022 at 14:59, Gert de Pagter wrote: > Hi Internals, > > I recently learned that using null safe on an array access can still > emit a warning when the array access is not defined. I kinda expected > it to work like a null coalesce and just short circuit there,without > the warning. > > Is there any chance this behaviour could be changed in a n upcoming > PHP version? I didn't see anything mentioned specifically about this > in the RFC. > > https://3v4l.org/1raa8 > > Greetings, > Gert de Pagter/ BackEndTea > This seems expected behavior to me: it's "nullsafe", not "undefinedsafe". If it operated like `??`, then `$undefined?->bar()` would be valid too, which seems wrong, IMO. Marco Pivetta https://twitter.com/Ocramius https://ocramius.github.io/
[PHP-DEV] Nullsafe array access can still emit a warning
Hi Internals, I recently learned that using null safe on an array access can still emit a warning when the array access is not defined. I kinda expected it to work like a null coalesce and just short circuit there,without the warning. Is there any chance this behaviour could be changed in a n upcoming PHP version? I didn't see anything mentioned specifically about this in the RFC. https://3v4l.org/1raa8 Greetings, Gert de Pagter/ BackEndTea -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
