Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113484 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 16334 invoked from network); 11 Mar 2021 19:04:48 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Mar 2021 19:04:48 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 46AC51804DD for ; Thu, 11 Mar 2021 10:57:22 -0800 (PST) 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.0 required=5.0 tests=BAYES_20,HTML_MESSAGE, SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: 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 ; Thu, 11 Mar 2021 10:57:21 -0800 (PST) Received: from wafer.home (unknown [IPv6:2a02:1205:5053:a220:55f4:e949:46da:f98f]) (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 79021150ED29 for ; Thu, 11 Mar 2021 19:57:18 +0100 (CET) Content-Type: multipart/alternative; boundary="Apple-Mail=_06ED7A6F-7AE0-4DD2-A0C4-7D8896C27B81" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Date: Thu, 11 Mar 2021 19:57:18 +0100 References: To: php internals In-Reply-To: Message-ID: X-Mailer: Apple Mail (2.3654.60.0.2.21) Subject: Re: [PHP-DEV] [PHP-DEV] [VOTE] Fibers From: cschneid@cschneid.com (Christian Schneider) --Apple-Mail=_06ED7A6F-7AE0-4DD2-A0C4-7D8896C27B81 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Am 11.03.2021 um 17:51 schrieb Chase Peeler : > If someone is willing to do the work to > add this to core, we aren't trading off other features in order to add = it, > and it doesn't cause BC breaks or other bugs, what is the reason to = not add > it? Complexity, which might come back and bite us in the long run. Note: I'm not talking about this specific feature, more in general. I = just wanted to point out that there can be reasons to *not* add = something even though it doesn't seem to have a drawback at the moment. - Chris --Apple-Mail=_06ED7A6F-7AE0-4DD2-A0C4-7D8896C27B81--