Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115398 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 92667 invoked from network); 12 Jul 2021 09:19:52 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 12 Jul 2021 09:19:52 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2DEC21804C9 for ; Mon, 12 Jul 2021 02:43:05 -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=-1.4 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, 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-ua1-f48.google.com (mail-ua1-f48.google.com [209.85.222.48]) (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 ; Mon, 12 Jul 2021 02:43:04 -0700 (PDT) Received: by mail-ua1-f48.google.com with SMTP id e22so2804518uaa.8 for ; Mon, 12 Jul 2021 02:43:04 -0700 (PDT) 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=t+nX+WFvKZgEmvtzgeOduOCI0cH2t8TYLmWQoPT+N2g=; b=rDDY3dl3C23Ewp1HpQ82KOWTBdRIAkXRdMY2xhI8ElQbE3sUKtMXOFLDdaXBpWGglv 96d586BHdnrLwUpGZBeMspCl48XQgGjt0ZQuBHKcQMI7bK/yKpSxVVcvZwJypAKk5f72 ugPh0jstgliQx6CjVzgK61uUF0bVvtMykU+D3iFrbDW1CEe9OHmtaZhQ6TkJ27eGY0Mb AW54ACf9UJESmyg1gtnDaUz3GcfXOk4QYGZs/noAM1vmVHh1UMnDC5PCTXt3tprDromv 5F/7J4TF1lB9mOSsXMxOMBqXsBV/M35/ouoWMXlWMI2iNAsLlMhVWdTtKM3++ntz+1g1 9/Rg== X-Gm-Message-State: AOAM530vGyys7oBgoNd9Im0ubfxVDZThmP2GTUitQoPqTu1oMLxp/MFC lKXwofYWdGuMFnSpYSYtUrueC0PzfJ/Q9A1odA== X-Google-Smtp-Source: ABdhPJyDBQSURiUZTQINTUIEqrHwmkwb0Hfoidr5k0GLdqVFBTTgH7q4I80/O1bHiULqxich8wJgRg31NMrDW3vPKb4= X-Received: by 2002:ab0:7027:: with SMTP id u7mr16769771ual.26.1626082982120; Mon, 12 Jul 2021 02:43:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 12 Jul 2021 11:42:51 +0200 Message-ID: To: Nikita Popov Cc: Pierre , PHP internals Content-Type: multipart/alternative; boundary="00000000000086506c05c6e9f2c2" Subject: Re: [PHP-DEV] Fake Closure Comparison From: patrickallaert@php.net (Patrick ALLAERT) --00000000000086506c05c6e9f2c2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le lun. 12 juil. 2021 =C3=A0 09:51, Nikita Popov a = =C3=A9crit : > I'm also not sure where this would be actually useful (though I'm okay > with including it, as the functionality itself seems sensible). As Patric= k > Allaert suggested this, maybe he can comment on some use cases. > I can't really see a useful case either, it was more rhetorical. For a feeling I can't explain much, I was caring less about: Closure::fromCallable('strlen') =3D=3D Closure::fromCallable('strlen') than: strlen(...) =3D=3D strlen(...) I know they are technically identical, but I see the first construct as a function call while the second one looks more like a language construct "referencing" (sorry for not using a more adequate verb) the same function. Anyway, I don't have a strong opinion on it. Regards, Patrick --00000000000086506c05c6e9f2c2--