Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122226
MIME-Version: 1.0
References: <kii8EchCRNKJRI1IgoTQGYbxr2d0_BNN6dm4QrEFnWNaWLaH68cG-GioF5j6ebhIJv5wAVKdHojWk5XJqk9z_yL4cA0Fmb1KD0P19VrCiXU=@gpb.moe>
 <344c3e06-3822-4b20-9a6f-a58fb64929a7@app.fastmail.com>
In-Reply-To: <344c3e06-3822-4b20-9a6f-a58fb64929a7@app.fastmail.com>
Date: Mon, 22 Jan 2024 20:30:32 +0100
Message-ID: <CAPTD5yHTJFO1aU_ES59bpYAqB+rGAOvHNvc93EA3i-_hojBTFA@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b2b945060f8ddd1c"
Subject: Re: [PHP-DEV] [RFC] Deprecate implicitly nullable parameter type
From: jorg.sowa@gmail.com (Jorg Sowa)

--000000000000b2b945060f8ddd1c
Content-Type: text/plain; charset="UTF-8"

> The only solution I can think of is to keep the deprecation in place
until PHP 10, but that's a very long time from now and the RFC says this
simplifies a decent amount of engine code, so I'm not wild about that idea.

Another solution is to have version 8.5. Also given the fact that much of
the deprecated code will be removed in PHP 9.0, maybe it's worth discussing
how long should be period between 9 and 10?

Kind regards,
Jorg Sowa

--000000000000b2b945060f8ddd1c--