Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115514 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 96102 invoked from network); 20 Jul 2021 08:47:47 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Jul 2021 08:47:47 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0D4281804AA for ; Tue, 20 Jul 2021 02:13:00 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-oo1-f53.google.com (mail-oo1-f53.google.com [209.85.161.53]) (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 ; Tue, 20 Jul 2021 02:12:59 -0700 (PDT) Received: by mail-oo1-f53.google.com with SMTP id x16-20020a4aea100000b0290263aab95660so4163026ood.13 for ; Tue, 20 Jul 2021 02:12:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9ASxzJ+alBSvKIjFzyVqO6+NTLz8Dldwt0yDX15KtTw=; b=l9AiQX83O7DQ+GTkufKv83ODj4GWTLnYpS5bVnDGAJSdOceBoQqtBIqEuSg8LdmMvt T4nvsW2Mo01szGlImcTa2nixzUGX5U3Za8Oalk8AFeBZWPe9OG11FtiPTIWucfkfSZFN PXm2H4C5+7IomgFhaItDdMixo1v+hnnwvq0qcQa6Dm6TohjqxRDeF32OI4oof6P29nsN Wixh032Yu8e6TeypGon3e4YGxX05XLyFJipz3wHJWPj6LYTuRKPKbbj5YSBd0sN+SN7r qRzspXWwFHif8U3daLgjqa2dqThB5cRi1RCd6kTN4Qo6G8m7VE3/IadodKpmAkHaPCMV lLuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9ASxzJ+alBSvKIjFzyVqO6+NTLz8Dldwt0yDX15KtTw=; b=VpSvYmAAwZBSl0s7BgzQtBfHlF76+jDrMIiWL1h33g6hAOJxSO+OMf24izZacSZ67J /LZlAl6R/Y7Nxy9Yf71Fr9z/KIj4ol1IO2tg7PjPR+s/j184ZocTJDsLZKg9kJSvA07V AX+pAULmnqGR+1ry01Cg7CHlyMvRRhM3X6TsX1Mum/ZLmrxAzejgojKvGwbeGhz3n5sL cN9q2zbLvZZ7PAVnvNEvrLIUBWRjArwx4Cs1s5GA7QAB3iq6CzHMVOlRBWUj87YXiPmm 9b6N+etKIxantRhNxsThP2JvB7HBNXuQN9vZzSSCkEZdWvvwn0nUir1EzF5s0M2VJaDV 40hA== X-Gm-Message-State: AOAM533RVDaq23xrrnIoPcG4nSiX1l313ChAK/YC3PoBVwrPzCDxx3d3 5X4dubiL3Y+3Fi5oIzAE3caECbZZrbHdHTTumblpskRbEwTuGuxo X-Google-Smtp-Source: ABdhPJyhQW5b5qwpS7HyQHYTBerIGM7Lrj98NrEMym71yqzqaK+wbZmcbuhNe9EpeKbXtTdnn1TIcNc4yp72IHcv/gc= X-Received: by 2002:a4a:498f:: with SMTP id z137mr20136641ooa.64.1626772378933; Tue, 20 Jul 2021 02:12:58 -0700 (PDT) MIME-Version: 1.0 References: <6a2ef792-9624-4355-ad08-dcc7bfa5e19f@www.fastmail.com> <83bdd8d9-9962-4995-9aff-4bd9b6b7e9b9@www.fastmail.com> In-Reply-To: <83bdd8d9-9962-4995-9aff-4bd9b6b7e9b9@www.fastmail.com> Date: Tue, 20 Jul 2021 11:12:47 +0200 Message-ID: To: Larry Garfield Cc: php internals Content-Type: multipart/alternative; boundary="000000000000c6deae05c78a75e7" Subject: Re: [PHP-DEV] [Vote] Pipe operator v2 From: ocramius@gmail.com (Marco Pivetta) --000000000000c6deae05c78a75e7 Content-Type: text/plain; charset="UTF-8" Hey Larry, On Sat, Jul 17, 2021 at 6:00 PM Larry Garfield wrote: > Hi Marco. Thank you for your explanation, even if I naturally disagree. > > Out of curiosity, what sort of additional > power/capability/flexibility/etc. would, in your mind, justify pipe or > similar being a native feature? PHP has a *ton* of native features that > *could* be done in user space, or are simply syntax sugar, but still wildly > popular and useful as native syntax. What is your heuristic for that? > > (The fact that there are 3-4 user space implementations of pipe-like > behavior, all incompatible, is one of the reasons why I think standardizing > it into a common core syntax *is* a good idea, though I know others > disagree.) > I think the pipe operator as a **custom** operator made sense when we had the entire discussion around placeholder parameters (`$$`) to be used in the pipeline. As a plain "chain of functions with one input parameter and one output", it makes little sense to have it as a custom construct, as it only adds complexity to the AST. Greets, Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ --000000000000c6deae05c78a75e7--