Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113779 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 32356 invoked from network); 25 Mar 2021 16:28:25 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 25 Mar 2021 16:28:25 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id CB01E1804D8 for ; Thu, 25 Mar 2021 09:24:28 -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_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) (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:24:28 -0700 (PDT) Received: by mail-oi1-f176.google.com with SMTP id a8so2659593oic.11 for ; Thu, 25 Mar 2021 09:24:28 -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; bh=kRARLxtEDb1dqlOCrTBLIYNsEZKRczRqLZ1OpgVl8nw=; b=rgRVASSA72usEyaQ5R4vqGoDVA3rOgb365VLogxl84nnTPPKhnINZiuY+MmJsE2n07 IQ3/jc3vPb0yTf02RYSJAM4AxUOq9NwYGONmAXSQa04ESTrL5qxgaPzQLwzdMtAa0RVG Gufa0cd+89AfIcZheooBmEPAZOleBbpmLs/22r1M704NVmrdoW10u5uW3UCnVIt4cIyL 6/bM/pTJ1nZtHttMWxhnzg2u1Z7E8du6f9IO/Re6b1hpnJ3+i9CeiG7yskFpRuIV1wFN jYiwn/d/yaX8vsVSaH69ZhkhsRKbL6CZiCxDvj6jfxjownN6V8UQGlZyKrvtPtKBq5Fi uV2Q== 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; bh=kRARLxtEDb1dqlOCrTBLIYNsEZKRczRqLZ1OpgVl8nw=; b=uXnVOkiyRDXFQbz99MFJOTR3XpDvwhDzKBzvgFZTiYiPsEZsgzrrAiYHu/GwRFm3Nw 5SDVhykDXoyFDbbBsiJApNVT5cqeA5hHoYx8gueYNScxpNb1wuWl2AtoJt+ApHCXkrDh ig2aKf8KvA32trvEDKeL50JFh1JM2uv1wLuRBibLgcXNBIObknA3jG4s4+O0WaffHkTU iBeahLrmV0BsnI8UygHK1U8sixHt9rha691ULqrvFEF7xe1gxZOFUbl00yxBeI9OIfGA fYhzMnKMFSja7sBzUdo3khHRgiD7DQcVeG0BUJcNzIRgn9jxTdY5sFcTYSNc8xkX2N0D GW0A== X-Gm-Message-State: AOAM532TuTGo15FPrV6AOm5E0HQhG9yy2X9aAEHDYbfGlkjrJyVxmpPk GJORIlUyAfKBnJe97DOYpW2j6vn6GiIqQ5shSqWQajUiWjsumibc X-Google-Smtp-Source: ABdhPJyz7OQi3VNAfzNo42WOCWWpBUicivEhqrhpWNoJr7RPQbGozxmtcQ+NysLyfA4EZXNfNLVAO8J9N4rfk0xamUk= X-Received: by 2002:a05:6808:2d6:: with SMTP id a22mr6759092oid.18.1616689466887; Thu, 25 Mar 2021 09:24:26 -0700 (PDT) MIME-Version: 1.0 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> <5D33D73A-6B75-456B-9774-91F71FF450BA@cschneid.com> In-Reply-To: Date: Thu, 25 Mar 2021 16:24:15 +0000 Message-ID: To: PHP Internals Content-Type: multipart/alternative; boundary="00000000000062cee305be5ed927" Subject: Re: [PHP-DEV] [RFC] Auto-capture multi-line closures andshortfunctions take 2 From: enunomaduro@gmail.com (Nuno Maduro) --00000000000062cee305be5ed927 Content-Type: text/plain; charset="UTF-8" Hi, Concerning the comments about what's exactly "auto-captured" by the scope of a multi-line short closure, we will be just reusing the "auto-capture" feature that already exists in one-line short closures. Therefore, this RFC doesn't have plans on changing the way "auto-capture" already works in PHP. --00000000000062cee305be5ed927--