Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109831 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 83973 invoked from network); 24 Apr 2020 16:43:27 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 Apr 2020 16:43:27 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A73911804CB for ; Fri, 24 Apr 2020 08:15:37 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00,BODY_8BITS, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS62371 185.70.40.0/24 X-Spam-Virus: No X-Envelope-From: Received: from mail-40137.protonmail.ch (mail-40137.protonmail.ch [185.70.40.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 24 Apr 2020 08:15:36 -0700 (PDT) Date: Fri, 24 Apr 2020 15:15:29 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1587741334; bh=q0BILWkksPjE5HWgyN8fj/DhSOlr95dt6HDwpDFtE8g=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=hQC1Kne+oS6jJhL1YVyelED4bCOzVdPDMUz7KfgMLeZwAiQZjwEKlwfFoHfE8thXO ZTNfox0oTcD0XCAxWqxkZIX8jIjr0LLTQkSS7GWkt8s2L62bAVXoi6RPu9XGPENnWu iB4/dz+xzVKpoGqwV8/6zxxgQvt+IQ9lrDfTAMh4= To: Markus Fischer Cc: "internals@lists.php.net" Reply-To: moliata Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Mixed type From: moliata@protonmail.com (moliata) I personally would stick to `mixed`. It's used extensively in the official = PHP documentation and has grown with the language. Heck, even static analysis t= ools and billions of PHPDoc comments (e. g. Laravel, CakePHP, Yii) use `mixed` t= ype. Switching to `any` just doesn't feel right. Oh and well, I also think that `mixed` makes more sense. 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 Friday, April 24, 2020 5:48 PM, Markus Fischer wro= te: > 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. wil= l obviously need to specify "allowing any type". As such the introduction o= f mixed is pretty much necessary. > > As in class Foo { =E2=80=A6 } $foo =3D new Foo; > > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >