Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114587 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 39346 invoked from network); 25 May 2021 13:00:33 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 25 May 2021 13:00:33 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7088D1804D9 for ; Tue, 25 May 2021 06:11:49 -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-lf1-f47.google.com (mail-lf1-f47.google.com [209.85.167.47]) (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, 25 May 2021 06:11:49 -0700 (PDT) Received: by mail-lf1-f47.google.com with SMTP id i9so46010813lfe.13 for ; Tue, 25 May 2021 06:11:49 -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=i8vQtBiopS/RY4C2V7Md7RcJUhv34fjgDx18B/GtggU=; b=Dmq82dKKCXs50YMYCTJgUPhzi/QkWuhB5M4D0n2T0rJc8XB5bMmut27pHpDXeA6RA/ rC2s/3kfoDDVAoR5PQaXO9FLPC3Vy/QCnFjrNXhSmfTFtIu7whjVC1XDS54l3mXoXU87 W4xWmDn0vjeTiSaZj4B8F0VODllU37BhCpomwOZgnyX2DFnZpsEnd2rfsWpY3OahW4xS YGlSQCp8WJIhsAtyrWWfeBvI2MNqoI/eNvECL99ZXarYq6ZU5U/eGt0g0rRP6AMTe8U5 7IWjZPmiEaNgNw0PNbJ6iGXXSHpPZjiAvDq3n42H7aXgPuhrmwjLZCpZDr99igZ3oqNY sXjA== 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=i8vQtBiopS/RY4C2V7Md7RcJUhv34fjgDx18B/GtggU=; b=OhTLpG5ophg2u4EBvyAq1YkLsFiRadJLyUiabUvUYCyof8OtMFo7+30BOo+m6cG4mh /D/ez7y3AEpoFOkiY9U4x1OcnjMgi11frlHQk+sQerhDU1sXcZisGo80O/sdWD15qiG8 fNrfN2iXwR4xQZ1p7S0bdfvmMM+TcLdHO6fTE1AbljD/X2Fi2oueO+TpwJoExB1n1gw/ fAlCZLQ7pFZmvZ1iqmQhDEfEnF5RZuDJuY+jQYJKO/evqSCTIdTv5V6q8VdaiIXoWUTu i6/GhGiR2ShHm8pvFpLJa0YSk01GSuxmRVf6l/vwGHIM1ye+J+I4RSWZWAEYLm+AwLY/ mv2Q== X-Gm-Message-State: AOAM533LRRXVQnSj2xDaGG9oCOpZAfWPv2fqtsOR9aaEdUmQezQ8rnbf zarLIFSMECXOXMylYkiS1vyn5xni6K/vK8Pn5A== X-Google-Smtp-Source: ABdhPJypJS2406PYLXHqtY/QN7qfwm9YvbnCSNp6fEeqOayrTvtvykeSqBZnOQ4Y5PMM94OhQRA+JcSwFGscjUXAWIg= X-Received: by 2002:a05:6512:992:: with SMTP id w18mr13519362lft.650.1621948305880; Tue, 25 May 2021 06:11:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 25 May 2021 15:11:37 +0200 Message-ID: To: Rowan Tommins Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary="0000000000009dbad005c3274444" Subject: Re: [PHP-DEV] [RFC] First-class callable syntax From: guilliam.xavier@gmail.com (Guilliam Xavier) --0000000000009dbad005c3274444 Content-Type: text/plain; charset="UTF-8" On Fri, May 21, 2021 at 10:08 AM Rowan Tommins wrote: > > Everyone: please let's keep this thread for talking about first-class > callables, and focus on the semantics not just the syntax - are there > edge cases we need to consider, downsides to the proposed > implementation, etc? > Well the semantics seem rather clear? We could say one "downside" is that new-expressions are not supported, but the RFC explains why ( https://wiki.php.net/rfc/first_class_callable_syntax#object_creation, I think it makes sense), and special-casing can always be added later (or in PFA). Regards, -- Guilliam Xavier --0000000000009dbad005c3274444--