Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119494
MIME-Version: 1.0
References: <18627e9c82d.1185ba82a2669697.6762525826203739336@wendelladriel.com>
 <CABAhh3EV4TAHjqx=g75qy0BrCsRj+XEu-yoZuzBAcqh-8+h7hg@mail.gmail.com>
 <8c3fb742-4367-0e4a-b96e-142657ac902c@gmail.com> <CAJpLVh3eG4d4rarpBhy5JMJeD_9ZDZiFLT7dQMRruLsCMTGsTQ@mail.gmail.com>
 <5edaa45e-08ff-9529-3a1b-42f655a68497@gmail.com> <CAJpLVh3-PNkJg0gJJGR9VG9S-XN-G0g_Q6VunhtbdDi-jzZoZA@mail.gmail.com>
 <a562b1a9-caaf-72fd-1fff-ff741dbbfcf1@demon-angel.eu> <CAAwdEzAv_Oztu2LUuazTOCiqmQXCDB0so6nX61JNpBoWTH3uYw@mail.gmail.com>
In-Reply-To: <CAAwdEzAv_Oztu2LUuazTOCiqmQXCDB0so6nX61JNpBoWTH3uYw@mail.gmail.com>
Date: Wed, 8 Feb 2023 17:22:52 +0000
Message-ID: <CA+1VZ8szB0OYJYddXEko5-aJbdwOUP6vLytEANvZ4S+vycYPgw@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000047a8c805f433841c"
Subject: Re: [PHP-DEV] RFC Proposal - Types for Inline Variables
From: wendelladriel.ti@gmail.com (Wendell Adriel)

--00000000000047a8c805f433841c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello everyone.
I created the Draft for this RFC:
https://wiki.php.net/rfc/local_variable_types
I'd love to hear your thoughts on this before proceeding further.
If anything should be changed or updated just let me know.
I'll be happy to help with anything related to this.

*---*
*Best Regards,*
*Wendell Adriel.*
*Software Engineer **| Investor | Amateur Photographer | Musician | INFP*
*https://wendelladriel.com <https://wendelladriel.com>*


Em qua., 8 de fev. de 2023 =C3=A0s 15:54, Alexandru P=C4=83tr=C4=83nescu <
drealecs@gmail.com> escreveu:

> On Tue, Feb 7, 2023 at 10:21 PM Mark Baker <mark@demon-angel.eu> wrote:
>
> > On 07/02/2023 20:53, Olle H=C3=A4rstedt wrote:
> > > No not really. I'd expect it behave similar to function argument
> > > type-hinting in PHP, that is, runtime checks, but where the notation
> > > can be used by external tools.
> >
> > The big difference is that the current checking for function arguments
> > is only necessary when a function is called; but that checking for
> > local-scoped variables would be required on every assignment to a
> > variable, or operation that can change a variable value; and that
> > becomes more problematic with the potential need for union types.
> >
> >
> Hi Mark,
>
> I saw that you and Olle were discussing that type checking should be
> similar with functions typed parameters .
> But in reality, it should be implemented more like typed properties.
>
> Actually that's already possible with something like
> https://3v4l.org/T6GFS
> function &declare_int(int $value) {
>     static $references =3D [];
>
>     $valueWrapper =3D new class(5) {
>         public function __construct(public int $value) {
>         }
>     };
>     $references[] =3D $valueWrapper;
>
>     return $valueWrapper->value;
> }
>
> $intVariable =3D &declare_int(0);
>
> $intVariable =3D 42; // works
> $intVariable =3D 'test'; // fails
>
>
> Even the PHP_INT_MAX works (it fails).
>
> To give credit, I saw it discussed few years ago on twitter and here you
> can see a nice playground implementation: https://github.com/azjezz/typed=
/
> I don't see a bug technical performance downside, other than the wrapper
> class references that you need to have a management for.
> I think an implementation in C would be not less performant than how
> properties types are checked.
>
> Regards,
> Alex
>

--00000000000047a8c805f433841c--