Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115352 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 79206 invoked from network); 7 Jul 2021 14:11:40 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 7 Jul 2021 14:11:40 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 29A4B1804DB for ; Wed, 7 Jul 2021 07:33:41 -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=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 ; Wed, 7 Jul 2021 07:33:40 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 963F1320091D for ; Wed, 7 Jul 2021 10:33:38 -0400 (EDT) Received: from imap43 ([10.202.2.93]) by compute1.internal (MEProxy); Wed, 07 Jul 2021 10:33:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=Bt6vwA 1abZgbOclhKsFEL0qIdcw8pkfFYpelFtZiOjw=; b=vCXpB62aKkhToMksRDmvOE B0J2uTkCvG+SF0auCg0IEdGMQ4HLr0txtOEDLTNg1n42kqwDU3bkaqGCI0fex0kT 7BHnfMe/Q8xQ6z1EygjP8e7/fccSz+vOpFl4PY9HMXPsmeqy9Hc6XZl2HhjAhDif bUZTmJPEYNjd1ELYOhLFeuK6cxxKmpTQBJfbQbNmGHrTOb+wIinJs6SqGr6rjLaY k6wPTQ4jCQOMDT4dhROQQqM7DVJ6gh9JQuwg/PKSMKDloj/xmHFUx2Y3h8q7xJ8R F90MNZW7qPkvbqxa4jg0dJGI8U3tcmhMmzjknv+n7SywBuMnDt4mS2/VcfelMjuQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrtddvgdejiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfnfgrrhhr hicuifgrrhhfihgvlhgufdcuoehlrghrrhihsehgrghrfhhivghlughtvggthhdrtghomh eqnecuggftrfgrthhtvghrnhepgeelgfekudeivddvteffueejffdthfejieevhefgffek udevkedtvdelvddvffefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheplhgrrhhrhiesghgrrhhfihgvlhguthgvtghhrdgtohhm X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id E7FADAC0076; Wed, 7 Jul 2021 10:33:37 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-531-g1160beca77-fm-20210705.001-g1160beca Mime-Version: 1.0 Message-ID: <2fba288f-ec2f-473d-9231-72cefb8659a7@www.fastmail.com> In-Reply-To: References: <6a2ef792-9624-4355-ad08-dcc7bfa5e19f@www.fastmail.com> Date: Wed, 07 Jul 2021 09:32:46 -0500 To: "php internals" Content-Type: text/plain Subject: Re: [PHP-DEV] [Vote] Pipe operator v2 From: larry@garfieldtech.com ("Larry Garfield") On Tue, Jul 6, 2021, at 6:54 PM, Bob Weinand wrote: > Hey Larry, > > there's still ongoing discussion on the semantics, and mirroring > implementation defined semantics from the implementation into the RFC > is not the way to go. The RFC should discuss reasons of why semantics > were chosen and the implementation then be decided upon it. Describing > it as "design artifact" is not okay. > I'm voting no at this point, to force it to be postponed to PHP 8.2 > with proper thought of what the semantics shall be. Possibly the > semantics are fine (I tend to disagree with the current ones, but > that's rather point for discussion), but they are not discussed enough, > especially as they only got described in the RFC in the last minutes > before the vote. The semantics around how references work with pipes have been consistent from April 2020 until today, aside from a few hours from when Nikita suggested blocking it to when I determined it was more work than I could handle on short notice. The RFC description of those semantics was clear and accurate for that entire time, modulo those few hours, and there was a test confirming them. So "they only got described in the RFC in the last minutes before the vote" is factually inaccurate. Wanting to think deeper about how references should work is fine, but please don't misrepresent the situation. How references work in this RFC has been explicitly defined since it was first introduced 15 months ago, and the first pushback on it at all as far as I recall came less than 48 hours before the feature freeze, leaving no time to have such a discussion. --Larry Garfield