Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120944
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
In-Reply-To: <245BD1CC-7D54-4CBE-9640-5C8FF5225617@gmail.com>
Date: Tue, 29 Aug 2023 22:19:40 +0900
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <DB4DCFB3-54EB-433B-AC1A-C1F923DDEFC3@sakiot.com>
References: <4406C50C-18FF-4F20-BA7B-206E86610CCC@sakiot.com>
 <245BD1CC-7D54-4CBE-9640-5C8FF5225617@gmail.com>
To: Claude Pache <claude.pache@gmail.com>
Subject: Re: [PHP-DEV] Apply strict_types to internal functions
From: saki@sakiot.com (Saki Takamachi)

> Hi,
>=20
> The larger issue is that higher-order functions do not inherit the =
`strict_types` mode from its calling code, and this is not specific to =
internal functions.
>=20
> If you intend to change that for internal functions (with proper =
deprecation period, of course), you might consider making such a =
behaviour also possible for userland functions (probably using some =
opt-in); so that future higher-order internal functions do not become =
impossible to polyfill.
>=20
> =E2=80=94Claude

Hi, thank you for confirming.

If you simply put the problem you pointed out in the code, would it be =
something like this?
https://gist.github.com/SakiTakamachi/8292dbfe92a2029a6c7b506b12296b7d

Admittedly, I don't think this is intuitive either.

However, if you always inherit the strict_types of the PHP file that is =
the starting point of processing, in most frameworks the settings in =
=E2=80=9Cindex.php" will affect everything.

When considering the inheritance of strict_types, I think that it should =
be an attribute that can be set in =E2=80=9Cphp.ini" instead of being =
specified for each file.

What do you think?

saki=