Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109829
To: internals@lists.php.net
References: <CA+kxMuQ4ZrNEC76Mi7SxqijmwzxRrHD1ATgVrPkbZicUx7=YcQ@mail.gmail.com>
 <VI1PR02MB4703953E17A1672FF8CD2947E2D00@VI1PR02MB4703.eurprd02.prod.outlook.com>
 <VI1PR02MB4703201DE0CF0C37A192D6A5E2D00@VI1PR02MB4703.eurprd02.prod.outlook.com>
Message-ID: <f457b377-33f3-055a-7ec8-ea7c59b989f9@fischer.name>
Date: Fri, 24 Apr 2020 16:48:59 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0)
 Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <VI1PR02MB4703201DE0CF0C37A192D6A5E2D00@VI1PR02MB4703.eurprd02.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Spam_score: -2.9
X-Spam_score_int: -28
X-Spam_bar: --
X-Spam_report: Spam detection software, running on the system "scanner01.home", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 
 Content preview:  On 24.04.20 16:33, Bob Weinand wrote: > Actually, Really had
    to laugh, reading your previous and then this mail :-) > > I forgot that
   for proper generics implementations, collections etc. will obviously need
   to specify "allowing any type". As such the introduction of mixed is pretty
    much necessary. > > As in class Foo<A, B> { … } $foo = new Foo<mixed, int>;
    > > As such, I'm actually in favor of introducing it. [...] 
 
 Content analysis details:   (-2.9 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0000]
X-CMAE-Envelope: MS4wfF4CjXFbQEdUMBMa3jofd41wX5dC15X9wrk3LOI8WC4txbS1q9cdUt/zF4ygEoawzyvY+K6Qr2MHTE8BXGQMeC6ibZpGHR86wT9AM5A4sVc5rwxVJfq5
 qlP6j+TY052i1TYB1Xgg2DipY1+od6Ckert+yshsP/WPLKWRkgCeqEZ0
Subject: Re: [PHP-DEV] [RFC] Mixed type
From: markus@fischer.name (Markus Fischer)

On 24.04.20 16:33, Bob Weinand wrote:
> Actually,

Really had to laugh, reading your previous and then this mail :-)


> 
> I forgot that for proper generics implementations, collections etc. will obviously need to specify "allowing any type". As such the introduction of mixed is pretty much necessary.
> 
> As in class Foo<A, B> { … } $foo = new Foo<mixed, int>;
> 
> As such, I'm actually in favor of introducing it.

Re-quote:
 > "allowing any type"

That would make the case for the `any` type instead of mixed; IMHO much 
more clear.

- Markus