Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109825
MIME-Version: 1.0
References: <CA+kxMuQ4ZrNEC76Mi7SxqijmwzxRrHD1ATgVrPkbZicUx7=YcQ@mail.gmail.com>
 <VI1PR02MB4703953E17A1672FF8CD2947E2D00@VI1PR02MB4703.eurprd02.prod.outlook.com>
 <CANS-=pf-RMwyh2BtJY-bScd6n12bW07HcsESvyjzrUagbCN34Q@mail.gmail.com>
In-Reply-To: <CANS-=pf-RMwyh2BtJY-bScd6n12bW07HcsESvyjzrUagbCN34Q@mail.gmail.com>
Date: Fri, 24 Apr 2020 14:29:31 +0100
Message-ID: <CALKiJKq92R22f0aFVD80eQGm6Qs4azf5JmaBChwODuTY4Op3fg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ac119805a4095b2e"
Subject: Re: [PHP-DEV] [RFC] Mixed type
From: rowan.collins@gmail.com (Rowan Tommins)

--000000000000ac119805a4095b2e
Content-Type: text/plain; charset="UTF-8"

On Fri, 24 Apr 2020 at 13:18, Lynn <kjarli@gmail.com> wrote:

> 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.
>


I realise it's partly a matter of style, but if I were benevolent dictator
of a legacy code base, I'd prefer to keep the docblocks, and mandate that
all uses of "mixed" should include a comment describing what the parameter
/ return type represents / is related to. Similarly, I wouldn't delete a
docblock for a return type of "array", because I'd want more specific
details (either using "type[]" syntax, "list<type>" syntax, or a comment
describing the "shape" of the array).

I'm not as strongly against adding "mixed" to the language as Bob, but I'm
not convinced I'd ever bother using it.

Regards,
-- 
Rowan Tommins
[IMSoP]

--000000000000ac119805a4095b2e--