Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120952
Return-Path: <saki@sakiot.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 4788 invoked from network); 30 Aug 2023 03:11:41 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 30 Aug 2023 03:11:41 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id B94431804D4
	for <internals@lists.php.net>; Tue, 29 Aug 2023 20:11:39 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS9370 160.16.128.0/17
X-Spam-Virus: No
X-Envelope-From: <saki@sakiot.com>
Received: from mail.sakiot.com (mail.sakiot.com [160.16.227.216])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256)
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Tue, 29 Aug 2023 20:11:38 -0700 (PDT)
Received: from smtpclient.apple (softbank060109141104.bbtec.net [60.109.141.104])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.sakiot.com (Postfix) with ESMTPSA id 5666C401FA;
	Wed, 30 Aug 2023 12:11:36 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sakiot.com;
	s=default; t=1693365096;
	bh=e/jW2oEevXrJdMl5w/p4PF5lK67XWE+U6mOvG1lPeyI=;
	h=Subject:From:In-Reply-To:Date:Cc:References:To:From;
	b=S+q3dTTyJWAgVG2+N1Xnr32LZhtW2mo03iD+5ICYEyHlFh75U6XW4aWG6fuPjig3s
	 gRLV8urMPvrQ7WhOnHTPHD51kTGWlgqE/8sDlds+DQEGnoFEg9vPCcHAZ+1FMBf1Pv
	 Jj6mcvTzkiqXAlmsi3IWEgVensfsKDA6/BZjLsP0=
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
In-Reply-To: <5B8A7736-9A2A-47E1-B410-4D734DC75EBE@gmail.com>
Date: Wed, 30 Aug 2023 12:11:23 +0900
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <FED392E6-9D77-4583-8EDB-F5BAACFDC534@sakiot.com>
References: <4406C50C-18FF-4F20-BA7B-206E86610CCC@sakiot.com>
 <245BD1CC-7D54-4CBE-9640-5C8FF5225617@gmail.com>
 <DB4DCFB3-54EB-433B-AC1A-C1F923DDEFC3@sakiot.com>
 <5B8A7736-9A2A-47E1-B410-4D734DC75EBE@gmail.com>
To: Claude Pache <claude.pache@gmail.com>
X-Mailer: Apple Mail (2.3731.700.6)
Subject: Re: [PHP-DEV] Apply strict_types to internal functions
From: saki@sakiot.com (Saki Takamachi)

> That might not be intuitive to you, but it follows directly from the =
specified semantics: whether a function is called in `strict_types` mode =
or not, depends only on where the function is called. I personally doubt =
that there is an easy way to adjust the rule in order to make it both =
=E2=80=9Cintuitive=E2=80=9D and simple.

On second thought based on your point, it seems confusing to change the =
behavior of strict_types only for calls from internal functions.
A minor problem is that there is no way to control strict_types for =
calls from internal functions.

Saki=