Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117415
Message-ID: <2abc84a5-0ca2-9431-0585-d3d6ee3df456@processus.org>
Date: Thu, 24 Mar 2022 16:20:27 +0100
MIME-Version: 1.0
Content-Language: en-US
To: Mark Niebergall <mbniebergall@gmail.com>
Cc: 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>
 <95fb2485-fa60-a107-5fd2-acdcef09bca3@processus.org>
 <CAKWdMui5cduh9MtQ1tv+N-Q6g+isfptNYmnpS3C0cm=yCjd_OQ@mail.gmail.com>
In-Reply-To: <CAKWdMui5cduh9MtQ1tv+N-Q6g+isfptNYmnpS3C0cm=yCjd_OQ@mail.gmail.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 24/03/2022 à 16:06, Mark Niebergall a écrit :
> So you are correct, the const value does have a value that has a type, but
> there is no way to enforce which type the value is or to use const with
> inheritance, which is part of the bigger picture here.

That was exactly my point: the type could simply implicitely be the one 
of the original value.

Then the engine just has to use the existing covariance/contravariance 
rules for type checks based upon the guessed value type. This would fix 
the type safety issue you are referring to.

--

Regards