Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122219
MIME-Version: 1.0
References: <kii8EchCRNKJRI1IgoTQGYbxr2d0_BNN6dm4QrEFnWNaWLaH68cG-GioF5j6ebhIJv5wAVKdHojWk5XJqk9z_yL4cA0Fmb1KD0P19VrCiXU=@gpb.moe>
 <CAO__Xv7b=db-k9=mmHc=V7bbqDy9nQuTYv-zVccPXkdU5H+OcA@mail.gmail.com>
In-Reply-To: <CAO__Xv7b=db-k9=mmHc=V7bbqDy9nQuTYv-zVccPXkdU5H+OcA@mail.gmail.com>
Date: Mon, 22 Jan 2024 11:45:36 +0100
Message-ID: <CANS-=pd3V8FsCPhF-6xcfgL9KtTz0-=hxtHFEM3nUEzy4yMkrQ@mail.gmail.com>
To: tag Knife <fenniclog@gmail.com>
Cc: "Gina P. Banyard" <internals@gpb.moe>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000035adec060f868936"
Subject: Re: [PHP-DEV] [RFC] Deprecate implicitly nullable parameter type
From: kjarli@gmail.com (Lynn)

--00000000000035adec060f868936
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 22, 2024 at 11:21=E2=80=AFAM tag Knife <fenniclog@gmail.com> wr=
ote:

> On Mon, 22 Jan 2024 at 09:51, Gina P. Banyard <internals@gpb.moe> wrote:
>
> > Hello internals,
> >
> > M=C3=A1t=C3=A9 Kocsis and myself would like to propose deprecating impl=
icitly
> > nullable parameter types.
> >
> > The RFC is available on the wiki at the following address:
> > https://wiki.php.net/rfc/deprecate-implicitly-nullable-types
> >
> >
> > Best regards,
> >
> > Gina P. Banyard
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: https://www.php.net/unsub.php
> >
> >
> Also just did a quick test, and i don't believe this would be possible. I=
t
> would remove functionality from the language widely used.
> As you are mistaking `iint $var =3D null` params as "nullable". Which the=
y
> are not, they are "optional default" parameters. The equals
> can be succeeded by any value, to set the parameter to such variable wher=
e
> the parameter is not passed. `int ?$arg` is not provided as
> an alternative, the directive `int ?$arg` simple allows the parameters to
> be passed as null, it is still required to pass through the
> parameter.
>
> To clarify
>
> `T ?$var` =3D Requires the parameter to be passed  to the function, null
> value allowed
> `T $var =3D null` =3D Does not require the parameter to be passed to the
> function, is set to null if not.
>
> https://3v4l.org/IWsqK


Your example contains `int2` as type with a default value of `null`. This
works because it implicitly marks the class `int2` as nullable. If you were
to set this default value to `1` via `int2 $int2 =3D 1` it breaks with "Fat=
al
error: Cannot use int as default value for parameter $int2 of type int2"

Anyhow, `=3D null` implicitly makes the parameter nullable even if the type
doesn't specify it's nullable. The argument is that if the type isn't
nullable, then the default value may not be null either.

--00000000000035adec060f868936--