Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115793 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 98060 invoked from network); 24 Aug 2021 18:29:00 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 Aug 2021 18:29:00 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 29D711804BE for ; Tue, 24 Aug 2021 12:03:02 -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-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ot1-f41.google.com (mail-ot1-f41.google.com [209.85.210.41]) (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, 24 Aug 2021 12:03:01 -0700 (PDT) Received: by mail-ot1-f41.google.com with SMTP id a20-20020a0568300b9400b0051b8ca82dfcso27898778otv.3 for ; Tue, 24 Aug 2021 12:03:01 -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=gn9dKhY6gx7fsDKbic36rkO80GepTMf+YMHbvMXFaI0=; b=mJvGwG2o6j10L+PHifMg5vCHU1jzQodOw2/DOP4i6o8Djqmu1JoKhozA/ly3R6UQVz 0txqbfVg7glsa5DJP1hcFT6B5j2WzUJuPZ5ka0BLVjg+Q9BPVoEbYtZXvt+gY8ugQchr 2ZOvKDYP1+o1Sdm3zrO0tDkt6bCTK8DvqqM9h0IYf3xXJStVUyGEVvDeSdtQneZMNKUa v8SVzg0FVM8eZTrFtr0Mr077p4pHO2yGh0c2Ls9dqiih9KHIMgQH9yDP/g4cq9UnUxc9 yCeyTlBcDSobE1lRSwkATfuYvxe86GhDW3TPG0oSjl13nwaQSlNADmL9q3uToYcLvHZt W1DQ== 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=gn9dKhY6gx7fsDKbic36rkO80GepTMf+YMHbvMXFaI0=; b=pm73fYBiRvWmA3pq4u5b1KoWhYhHgO60Y01ImMimNvVER3LjPYogaSGiW7fwm02vz5 53JlF+QrOB2EzDTbF/eL0Yh38x7XLE4OIlxIuBhof7aP1foriF2lq2+zd4eL5kvVNSec FRzubj5U3xqXh2pZnjpliBBbOhzyePxPxzr1syGp0o7Dfk20AkTx1VekVsIzEiHeuxgg bvWeP/7JlLgKVjX5IlJXoyMvibH46kDmq1ONtXhsdX0cLYEj45eRxdFn/KvRI9jx37xm 8WyOgw9yVRkAPQzP5u4SanBtNlDD1hehxCAnwIfYSQiZFufd9REr4H/pYKE0S/P6prT5 z8Zg== X-Gm-Message-State: AOAM530V4McOU243c97PV2NZuoUeCuGGalFZRUFtSUl8fsF0cyES6tsG nm0Ftguu2mAI5M3PKJPHQ1YrqE6jUx7mJLlSkj0= X-Google-Smtp-Source: ABdhPJzxqSSWI+WFDQwQlyeXRwZYe4C+L3TXjchWcmrohOYGqdc0QZ9NrFoedWxfav3KWJfh82bqB2h2N/d2qg0/zhw= X-Received: by 2002:a05:6808:281:: with SMTP id z1mr3870619oic.30.1629831778694; Tue, 24 Aug 2021 12:02:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 25 Aug 2021 02:02:45 +0700 Message-ID: To: Dan Ackroyd Cc: tobias.nyholm@gmail.com, PHP internals Content-Type: multipart/alternative; boundary="0000000000003677c805ca52c857" Subject: Re: [PHP-DEV] Guidelines for RFC post feature-freeze From: pierre.php@gmail.com (Pierre Joye) --0000000000003677c805ca52c857 Content-Type: text/plain; charset="UTF-8" good evening Dan, First of all, could you please not merge many different mails in one single reply? Thanks. On Wed, Aug 25, 2021, 1:43 AM Dan Ackroyd wrote: > Pierre Joye wrote: > > Many additions went through while being incomplete. > > > For almost all recent RFCS > > related to syntax, arguments/return types or properties, I don't think > > it justifies being added while being incomplete. > > I think you are remembering how changes were made to PHP through rose > tinted glasses. > Not really, or actually not at all. Quite the opposite. Pretty much all of the improvements to PHP's type system were > 'incomplete' but they were still huge chunks of work, and some of them > only just got accepted. This implies that this statement is more accurate than the one in my reply. Suggesting that (other) people need to do more work to satisfy the > level of quality you want in an RFC is a good way of stopping any > major progress from being achieved. > I think there is a misunderstanding here. PHP is not at a stage where what is missing are easy additions like simple scalar return types. As the recent discussions show, it needs more time to design, plan and implement the desired additions. This is why so many languages having reached this level of maturity are extremely prudent when it comes to very long term syntax or features additions. Seeing as a lot of RFCs that improve PHP's type system seem to be the > last RFC before someone decides to not bother contributing any more, I > strongly suggest not trying to make it more difficult to get > improvements made. > I understand your concerns and similar concerns have been brought when we introduced, you guess it, the RFC process. What I am talking about here is to have more clarity and stability how such critical additions are approved, or not. Critical not because of the needs but the permanent state of such additions. And more importantly, how they are designed to begin with. This is rarely a short journey nor a one person show. It is hard to have a diverse group with enough time, knowledge and motivation to work on such ungrateful tasks (but challenging). Such events create exactly what your comment is saying. best, Pierre --0000000000003677c805ca52c857--