Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121521
MIME-Version: 1.0
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>
 <CAPzBOBPu3y3-WqoUSLj7me7ce0U5S6vFUK-E-PxgWr-tys0L9Q@mail.gmail.com> <CAFPFaMJJywVq=p1tAUey2WY1XzFPKWjjek7LL37fs73vZHwUHA@mail.gmail.com>
In-Reply-To: <CAFPFaMJJywVq=p1tAUey2WY1XzFPKWjjek7LL37fs73vZHwUHA@mail.gmail.com>
Date: Mon, 30 Oct 2023 09:46:11 -0300
Message-ID: <CAGS0MVBRsQ3vYsW_VLP-Z2dnTRePaV4_tXw_6+4Dy1=p+Bn8=Q@mail.gmail.com>
To: "G. P. B." <george.banyard@gmail.com>
Cc: Robert Landers <landers.robert@gmail.com>, =?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?= <drealecs@gmail.com>, 
	Oladoyinbo Vincent <oladoyinbov@gmail.com>, Mike Schinkel <mike@newclarity.net>, 
	Larry Garfield <larry@garfieldtech.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000707da00608ee6ea9"
Subject: Re: [PHP-DEV] Re: Basic Type Alias
From: ericklima.comp@gmail.com (Erick de Azevedo Lima)

--000000000000707da00608ee6ea9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

File-based are the worst.

Let the types be attached to namespaces. As we have autoloaders, everyone
is free to load them however they want (PSR-4, file, custom autoloader,
whatever).

Best regards,
Erick

Em seg., 30 de out. de 2023 =C3=A0s 08:34, G. P. B. <george.banyard@gmail.c=
om>
escreveu:

> On Sun, 29 Oct 2023 at 20:36, Robert Landers <landers.robert@gmail.com>
> wrote:
>
> > My personal opinion is that file-based type aliases would be the best.
> > It solves an immediate problem while introducing a problem most people
> > will never have (needing to reuse the type aliases elsewhere). It
> > allows them to be used in functions and classes, while also making
> > code more readable but not opaque outside the file. For example, if
> > there is a type called BigNumber that was an alias of
> > GMP|int|float|string, outside the file, knowing the actual types in my
> > IDE is more useful than "BigNumber" and doesn't require me to dig into
> > the definition or even agree with the other file's definition of
> > "BigNumber." I just need to know that I need to pass it one of those
> > types from my own code. However, reading that file's code, I don't
> > need to know the intimate details of the aliases to make it more
> > readable.
> >
> > If we find ourselves constantly writing the same type aliases in a
> > bunch of files, we only need to wait less than a year to implement
> > "global" (as in, available once include'ed) in the very next version
> > of PHP.
> >
>
> No, this is actually ridiculous. File based type alias are dumb and I wil=
l
> vote against this.
> My main motivation to work on function autoloading in the first place was
> to create a mechanism so that adding a new type autoloader is very easy.
> As I already find the semantics of one interface per file dumb, let's not
> make it even more ridiculous of having a single line in a file, especiall=
y
> as a library/project will likely want to declare more than one type.
>
> An IDE should very much have no struggle to resolve what the type alias
> actually resolves too, they already do this with classes and interfaces.
> And needing to declare every alias in every single file of a project is a
> ludicrous idea.
>
> Best,
>
> Gina/George P. Banyard
>

--000000000000707da00608ee6ea9--