Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113785 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 43386 invoked from network); 25 Mar 2021 16:54:32 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 25 Mar 2021 16:54:32 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 9E4151804D8 for ; Thu, 25 Mar 2021 09:50:31 -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,NICE_REPLY_A, 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-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.51]) (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, 25 Mar 2021 09:50:31 -0700 (PDT) Received: by mail-ej1-f51.google.com with SMTP id l4so4018518ejc.10 for ; Thu, 25 Mar 2021 09:50:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=qzmi+1hsCOtSav66OKRql8pzTVfO5fPD8184A2JlE68=; b=TB5sSl/7w90DZm5M06s9AkJiPhcTTblz9jqKftjNqqagWcDjsm4d5qCKD043QvOy/I CiF3fEhUPPCFUhnJdW9T6FVMIw8DMOnTIgyqonUAw+UMmBFLwLDmmEPdwBqMxUilEOwo BilPcOf4yOnHLTSO6PdTV+1WFV7pXMZoCdAlbhNV91/wV3k49xgG1zR9lgvs8VIJj6dt 0IjRJ/Fd02whE2XVkqIJaBWNA37yvIU7B34crlw6pBSmSukGlLLGb6iYc5PdFQi9M7ea cz8vxvPb8eqBqm7BdX4LOgAt5u9F3ilpOYWVcffoWAljXvp13p66F0qyGMbpdSr4cdll Wg8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=qzmi+1hsCOtSav66OKRql8pzTVfO5fPD8184A2JlE68=; b=sbiXYaDrchcxsNKzgtguLBQsrgVcX4LpR1dgpnvBt6h57pYaDAW3aVGYucIxz3sLbQ OqEojsMnPHZd19+ZkPxN2nQRSv3XGE8ps+PMFW3qtRio2VazFRs+m6cYudMcYTXIrD9k r7doH0ImzxC8Z/ZfrJNUmNJXdtO0ZooYd2FTy3kzF5d/X/PaExr02iHWhknvXNbZbzjN I00aOUhUfK8uuvW7V4nSzuJ2UJT7SE1WE9uhI+4nG8Ztp68Fjef60JR3yFLHHSK2oBzN rIG8hHnWSZmVxhPhJZtTHSpR0tsUfnB8vzDtCsTrZN01wEPOv3q9re0qxriHghiaK/48 Mzhw== X-Gm-Message-State: AOAM532GFG+h9jKxTLQqvcLB9yjoRZPoVABh70TYW1/3O1LEeomOH9Gk qai4vdJiJVFyEBS+0kLePMsnpGFuZ7k= X-Google-Smtp-Source: ABdhPJwHURUButci94neWn2d7hf6PU7ZMkKTMJARHDC4KX6/3QwiQh1R8SS3bJSerfONROVy/Q7WpQ== X-Received: by 2002:a17:906:53d7:: with SMTP id p23mr10573074ejo.140.1616691029243; Thu, 25 Mar 2021 09:50:29 -0700 (PDT) Received: from [192.168.0.22] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.googlemail.com with ESMTPSA id v8sm2939052edx.38.2021.03.25.09.50.28 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 25 Mar 2021 09:50:28 -0700 (PDT) To: internals@lists.php.net References: <88c9eb5f-f80c-4869-b7f8-1b58b9e2eaa3@www.fastmail.com> <4DC3B66E-A91A-4AA9-8872-8EE9DE92C2D4@cschneid.com> <8c72c162-83c0-7c7f-2fa7-4fbe3fb30a4a@gmail.com> <605bae82.1c69fb81.f49f7.d11eSMTPIN_ADDED_MISSING@mx.google.com> <919e30e7-3e5e-d955-7bb4-1e1b5825cdd1@gmail.com> <635DD146-FC6F-4991-8D2C-5A6B492722D5@newclarity.net> <734f12de-da98-6b76-c2fe-8682f4d177aa@gmail.com> <36E45DD6-E2BD-4801-BAAE-4355C83D1AC3@newclarity.net> Message-ID: Date: Thu, 25 Mar 2021 16:50:28 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <36E45DD6-E2BD-4801-BAAE-4355C83D1AC3@newclarity.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB Subject: Re: [PHP-DEV] [RFC] Auto-capture multi-line closures and shortfunctions take 2 From: rowan.collins@gmail.com (Rowan Tommins) On 25/03/2021 15:02, Mike Schinkel wrote: > Can you please clarify why "function(...) use(...) {...}" can't be their solution when someone needs by-reference capture? For the same reason - or lack of reason - why it can't be the solution when they need by-value capture. In other words, whatever reason people have for wanting this RFC. Regards, -- Rowan Tommins [IMSoP]