Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109779
Date: Wed, 22 Apr 2020 16:56:42 +0000
To: Dan Ackroyd <Danack@basereality.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Reply-To: moliata <moliata@protonmail.com>
Message-ID: <6pYNtxu_0sImXziqQJB6p3nOYx-Dca_fdrTkfvjpHD9XxmWioPFZ01x44xk1n071D-MxZX16_8mEFrzqRVmTgecqDWsxnivqjsiei4KSTbw=@protonmail.com>
In-Reply-To: <CA+kxMuRMXtnqkE1EH4knj=JmyMhKQeWC+rp9=J5nY6bZHs4wLQ@mail.gmail.com>
References: <AG6mBe5pFAi6EzBs269tNFsDoOmnW-qjSfHkugdR8AZPM2nRXUuNYl8uGQC8a15XqmVHd5PwoZuCezJDr_j2HG8a7qGF728G0sG8AF6DkgQ=@protonmail.com>
 <CA+kxMuRMXtnqkE1EH4knj=JmyMhKQeWC+rp9=J5nY6bZHs4wLQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Typed callable properties
From: moliata@protonmail.com (moliata)

Hello,

thank you for your opinion. In response to you mentioning that fixing this
problem would be a huge amount of work, I would like to reiterate the idea =
of
simply ignoring context-dependent problems for the time being. In fact, we =
can
observe this behavior in parameter/return type hints already. As such, it
doesn't make sense to make just property type hints a special case/exceptio=
n.

Moreover, I oversaw Sara Golemon's comment in the `mixed pseudo type` RFC t=
hat
she would like to use type aliasing and union types instead, at least in th=
e
long run. The problem that comes up with this approach is that even if we d=
id
something like this:
`use mixed as string|int|...|callable;`
...we couldn't apply this `mixed` type alias to properties as callable type=
 is
not allowed to be used with them.

Best regards,
Benas Seliuginas

=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me=
ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
On Wednesday, April 22, 2020 5:29 PM, Dan Ackroyd <Danack@basereality.com> =
wrote:

> On Tue, 21 Apr 2020 at 14:08, moliata moliata@protonmail.com wrote:
>
> >
>
> > I wanted to ignite a friendly discussion whether
> > PHP should allow typed callable properties.
>
> IMO no.
>
> Trying to fix the problems with callables would be a huge amount of
> work, and not actually give that much benefit. Even just documenting
> the problems with callables* is a non-trivial amount of work, and I
> suspect there are many horrors lurking with the SPL code related to
> them.
>
> > I believe we should look into...
>
> I'm pretty sure that choosing a different problem to solve that:
>
> -   would be easier to solve.
> -   provide more benefit in the long term.
> -   not require breaking a lot of userland + internal code immediately,
>     but instead allow for migration over a longer period.
>
>     My thoughts on adding 'function types' are here:
>     https://github.com/Danack/FunctionTypes/blob/master/function_type_rfc=
.md
>
>     There's still more than a couple of known problems that need to be
>     worked through, as well as probably unknown problems lurking. As emai=
l
>     is not a good format for carrying out discussions, if people want to
>     take part in that discussion, doing it in that repo would be better
>     imo.
>
>     Assuming the problems remaining can be addressed, that would give us =
a
>     more useful feature, and the existing 'callables' can be slowly
>     deprecated and maybe removed from PHP in the distant future.
>
>     cheers
>     Dan
>     Ack
>
>     *[problems with callables] - https://wiki.php.net/rfc/consistent_call=
ables
>