Re: [RFC] Mixed type
| From: | moliata | Date: | Fri, 24 Apr 2020 16:02:18 +0000 |
| Subject: | Re: [RFC] Mixed type | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-109834@lists.php.net to get a copy of this message | ||
Hello,
I did some tests and in fact it seems you're right. Thank you for letting me know, didn't
know!
Best regards,
Benas Seliuginas
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, April 24, 2020 6:44 PM, Marco Pivetta <ocramius@gmail.com> wrote:
> Hey moliata,
>
> On Fri, Apr 24, 2020 at 5:27 PM moliata moliata@protonmail.com wrote:
>
> > Actually, it's not quite possible to declare a
mixed
> > type using union
> > types given that it's not possible to make properties as callable (please
> > take a look at my "Typed callable properties" post in the mailing list).. As
> > such, if we wanted to make a property hold a callable, we would have to
> > fallback to just not using a type hint at all.
> > Correct me if I'm wrong but this behavior is addressed in the RFC and we
> > can pass callables to properties that are declared as
> > mixed, right?
>
> The only limitation right now isresource:
> callable is always either an
> array, a string or an
> object that implements __invoke, so
> callable is a subtype of the union type mentioned few posts
> above.
>
> Marco Pivetta
>
> http://twitter.com/Ocramius
>
> http://ocramius.github.com/