Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109824
MIME-Version: 1.0
References: <CA+kxMuQ4ZrNEC76Mi7SxqijmwzxRrHD1ATgVrPkbZicUx7=YcQ@mail.gmail.com>
 <VI1PR02MB4703953E17A1672FF8CD2947E2D00@VI1PR02MB4703.eurprd02.prod.outlook.com>
In-Reply-To: <VI1PR02MB4703953E17A1672FF8CD2947E2D00@VI1PR02MB4703.eurprd02.prod.outlook.com>
Date: Fri, 24 Apr 2020 14:18:07 +0200
Message-ID: <CANS-=pf-RMwyh2BtJY-bScd6n12bW07HcsESvyjzrUagbCN34Q@mail.gmail.com>
To: Bob Weinand <bobwei9@hotmail.com>
Cc: Dan Ackroyd <danack@basereality.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000032444705a4085dc9"
Subject: Re: [PHP-DEV] [RFC] Mixed type
From: kjarli@gmail.com (Lynn)

--00000000000032444705a4085dc9
Content-Type: text/plain; charset="UTF-8"

On Fri, Apr 24, 2020 at 2:12 PM Bob Weinand <bobwei9@hotmail.com> wrote:

> Mixed is in almost every case just patching the holes in PHPs type system.
> And as such, I'd rather promote RFCs trying to properly fix the gaps in the
> type system than supporting mixed.
>
> Mixed is a hack, do not use mixed.
>

Heya Bob,

I maintain lots of legacy code and I cannot add return types despite being
truly mixed. Mixed is not a hack, it's a scenario that frequently happens.
There are lots of use-cases where we explicitly want to mark it as such as
it truly accepts anything. Would I use it in new code? Pretty much never,
as `string|int` would already cover the majority of cases, especially where
ints are represented by strings.

I would love to see mixed being added as it lets me remove a lot of
docblocks that are only added so I can indicate mixed. I disagree that it's
patching holes, it's filling a gap that's currently missing something.

Regards,
Lynn

--00000000000032444705a4085dc9--