Does this RFC support __get() returning by reference?
See
https://github.com/php/php-src/blob/master/Zend/tests/overloaded_prop_assign_op_refs.phpt#L11
Thanks. Dmitry.
On Mon, Jun 1, 2020 at 12:20 AM Gabriel Caruso
wrote:
> On Sun, 31 May 2020 at 15:57, Nikita Popov wrote:
>
> > On Fri, May 29
Hello Internals,
I'd like to know what would be people's feelings towards having a `numeric`
type. I remember reading the nullable casting RFC (
https://wiki.php.net/rfc/nullable-casting) and it's discussion (
https://externals.io/message/105122). Although I would very much prefer to
have nullable
Hi Marco,
On Tue, 2 Jun 2020 at 16:10, Deleu wrote:
>
> The primary intent would be to safely pass around input that usually comes
> from HTTP, CI or Database. Whenever interacting with these data providers,
> string is a common format. `is_int` will not return true for integer values
> that are
Hi internals
I'd like to introduce another RFC I've been working on:
https://wiki.php.net/rfc/nullsafe_operator
It introduces the nullsafe operator ?-> that skips null values when
calling functions and fetching properties. In contrast to the last few
attempts this RFC includes full short circuiti
Thanks for your input!
On Sat, May 30, 2020 at 8:36 PM Dan Ackroyd wrote:
> For my own code, I convert all non-silenced errors and warnings into
> an exception through the error handler*. That works pretty well, but
> has one big downside - it only throws one type of exception.
>
> I wrote some
On 02/06/2020 22:52, Ilija Tovilo wrote:
It introduces the nullsafe operator ?-> that skips null values when
calling functions and fetching properties. In contrast to the last few
attempts this RFC includes full short circuiting.
I like it a lot! Concise and clear RFC.
From having used a simi
