Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117398
Return-Path: <cschneid@cschneid.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 62208 invoked from network); 22 Mar 2022 14:04:40 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 22 Mar 2022 14:04:40 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 4837018037E
	for <internals@lists.php.net>; Tue, 22 Mar 2022 08:31:09 -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=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE,
	SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no
	version=3.4.2
X-Spam-ASN: AS1836 195.49.0.0/17
X-Spam-Virus: No
X-Envelope-From: <cschneid@cschneid.com>
Received: from darkcity.gna.ch (darkcity.gna.ch [195.49.47.11])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Tue, 22 Mar 2022 08:31:08 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a02:1210:2ea4:cf00:30ff:ed5:a1b0:d2ab])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by darkcity.gna.ch (Postfix) with ESMTPSA id 242F41516680
	for <internals@lists.php.net>; Tue, 22 Mar 2022 16:31:06 +0100 (CET)
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Date: Tue, 22 Mar 2022 16:31:05 +0100
References: <CAESVnVq80gzujeb_DsfH9hU5Q+YVQcAYF+siLZSiQOC2cxDBqw@mail.gmail.com>
 <1289b56c-e766-4889-bbb2-06abb4e63a6d@www.fastmail.com>
 <CABdc3WrSUjPSA+XqHv1bGi_1kvr6ampfg4ggS9tZwgRSFpvG=A@mail.gmail.com>
 <CAPzBOBMQSEzMeGvS=dJfbPKsYT7JhF5O5hL7WEs-ivE3kgsJ3A@mail.gmail.com>
 <CAESVnVo4aCeaQe5Vsi858G9X02nkh0qsX73K-XQJ5M3qvrFNrg@mail.gmail.com>
To: php internals <internals@lists.php.net>
In-Reply-To: <CAESVnVo4aCeaQe5Vsi858G9X02nkh0qsX73K-XQJ5M3qvrFNrg@mail.gmail.com>
Message-ID: <3496914D-AF9A-48FD-B37C-DCA54CB32AFA@cschneid.com>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Subject: Re: [PHP-DEV] Discussion: String streams
From: cschneid@cschneid.com (Christian Schneider)

Am 22.03.2022 um 16:14 schrieb Sara Golemon <pollita@php.net>:
> So while I said I wanted to avoid the firestorm suggesting userspace
> overloading would bring, maybe that's the question to ask:
>=20
> Who's just a hard-nope on userspace operator overloading?  If your =
reasons
> go beyond foot-gun (and that is a valid reason), could you share what =
those
> reasons are?


An obvious one could be complexity.

In the discussion about warning in conjunction with type juggling it was =
mentioned that this leads to increased complexity in the PHP core. While =
my knowledge of the engine is too superficial to really know I'd assume =
that generic operator overload could lead to quite some additional =
complexity and/or overhead.

But I'm sure other people know better than me what the real costs are.

Regards,
- Chris