Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117410
Message-ID: <95fb2485-fa60-a107-5fd2-acdcef09bca3@processus.org>
Date: Thu, 24 Mar 2022 08:03:55 +0100
MIME-Version: 1.0
Content-Language: en-US
To: Larry Garfield <larry@garfieldtech.com>,
 php internals <internals@lists.php.net>
References: <CAKWdMuh=qmE1==KnqqPX-yeNh5oObxFrVcaZ_LNUW+rFzqbN-A@mail.gmail.com>
 <76c399cb-fb29-4583-a212-8eb69740c96b@www.fastmail.com>
In-Reply-To: <76c399cb-fb29-4583-a212-8eb69740c96b@www.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Typed constants revisited
From: pierre-php@processus.org (Pierre)

Le 23/03/2022 à 23:10, Larry Garfield a écrit :
> Is there a benefit to it other than "well everything else has types now, so..."?  Even if it's esoteric, like in reflection-based meta programming?  (I've been dabbling too much in that lately. :-) )  "Everything else does" isn't a compelling argument for me, but there may be others I'm not thinking of.
>
> --Larry Garfield
>
Hello,

Well I was thinking myself that const being well... constant, and so 
always defined, type could be determined at compile time without the 
need to express it in a verbose way.

PHP doesn't do any static type inference, but in this case, it could be 
done almost for free, am I wrong ? If it was determined at compile time, 
then the type checking on overrides would only be trivial, using the 
parent occurrence value inferred type. My point is that there's no need 
to express the type of a value, the value has already has a type.

Regards,

--

Pierre