Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121511
MIME-Version: 1.0
In-Reply-To: <CAAwdEzCGYHukrU+tF3vEzKxx3rcVK32W1H_kBf=4j9rupKx+KA@mail.gmail.com>
References: <CAHXoPRtjsPzgpYnhB05hjdZo6Q-MDr4TUGbn9LQ77-hKVTCZOA@mail.gmail.com>
 <e94b0021-b18d-4c48-8764-6d4909142b26@app.fastmail.com> <ED1ED859-FC81-442D-9A30-EE8D0C639FFD@newclarity.net>
 <CAHXoPRtSEBPEFf1FrkwfqK_keFd7crvACBpm23etZ0ajNz6DDg@mail.gmail.com> <CAAwdEzCGYHukrU+tF3vEzKxx3rcVK32W1H_kBf=4j9rupKx+KA@mail.gmail.com>
Date: Sun, 29 Oct 2023 12:49:26 -0700
Message-ID: <CAHXoPRvbr7Nb-YSH=i96PeO51fD2fozJZY437E-foc7Lr8i3Hw@mail.gmail.com>
To: =?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?= <drealecs@gmail.com>
Cc: Mike Schinkel <mike@newclarity.net>, Larry Garfield <larry@garfieldtech.com>, 
	php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001e343a0608e03851"
Subject: Re: Basic Type Alias
From: oladoyinbov@gmail.com (Oladoyinbo Vincent)

--0000000000001e343a0608e03851
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

So, who is going to help with the implementation :)

On Saturday, October 28, 2023, Alexandru P=C4=83tr=C4=83nescu <drealecs@gma=
il.com>
wrote:

> Hey,
>
> So actually while reading this:
>
> On Fri, Oct 27, 2023 at 11:42=E2=80=AFPM Oladoyinbo Vincent <oladoyinbov@=
gmail.com>
> wrote:
>
>> And also, in order to group and namespace the Type Alias, i suggest we u=
se
>> `typedef`, like i specify in my last message, it will be like this:
>>
>> File A.php:
>>
>> ```php
>>
>> namespace Package;
>>
>> typedef MyTypes {
>>
>>     type Numeric: int|float|null;
>>
>>     type Chars: string|null;
>>
>>     type Result: bool|null;
>>
>> }
>>
>>
>  I came up with an idea:
>
> In php we don't have inner/nested classes, like in Java.
> But maybe at some point we could have. An inner class would help with
> avoiding some extra files and autoloading, especially when that class wou=
ld
> be needed as private.
>
> Coming back to types, what if a type would be allowed to be defined on th=
e
> class level?
> It would solve the autoloading problem as it would be loaded together wit=
h
> the class.
> And I guess that in real-life, complex types are usually related to some
> code using them, so I expect that identifying a class where the type to b=
e
> placed would not be hard.
> And even if it would be difficult, There can always be a class named Type=
s
> that would have only type definitions.
>
> An example would look like this:
>
> namespace My\App;
> class Types {
>     public type Numeric: int|float;
> }
>
> And it could be used with:
>
> use My\App\Types.Numeric;
> function castNumericToFloat(Numeric $number): float {
>     return (float)$number;
> }
>
> or
>
> use My\App\Types;
> function castNumericToFloat(Types.Numeric $number): float {
>     return (float)$number;
> }
>
> or by using an import alias, of course.
>
> Maybe we can use this construct, along with allowing a type to be defined
> in a normal way, a way that would not permit autoloading.
> However, a way that would better fit code that is procedural and it can b=
e
> loaded in the same functions.php that some projects use.
>
> Allowing inner "types" on classes might be a bit more complex that I can
> ever evaluate.
> But it might open the door for inner classes and there are nice construct=
s
> that can be built using this.
>
> Regards,
> Alex
>

--0000000000001e343a0608e03851--