Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120803 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 69621 invoked from network); 13 Jul 2023 12:23:17 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 13 Jul 2023 12:23:17 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 06D791804A7 for ; Thu, 13 Jul 2023 05:23:16 -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, T_SCC_BODY_TEXT_LINE 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-vk1-f181.google.com (mail-vk1-f181.google.com [209.85.221.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 13 Jul 2023 05:23:15 -0700 (PDT) Received: by mail-vk1-f181.google.com with SMTP id 71dfb90a1353d-4812dc50608so8286e0c.1 for ; Thu, 13 Jul 2023 05:23:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689250995; x=1689855795; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KfgGwC6OQ1VQH6VfXv/s/6WQtbuBLu+ynhFeWV7RfAA=; b=hvqi8YYu4ecGZaF232EyFgVpqXnc0iHRdCLP30pBD7lsFBlaNLgEYjC1p7InL9+loV Ch295zzZYKgRxN33kqkqo8STJpgcu/OT1J9U1/slDvPXMQiMzOfep7qg5xDq8SDGClRu tpjg6h/UY5X6zpCMjiTJGsdhn23drMKIKeAWzaG7izlbrgnirzYLETElzDnIlXSWPbHi T8diKSPJUUvPzUzWQmoJtk3/Lz/U6qAIz9v+kbmiAEQccG0b28u5uMGeoDKnS9bIkAS6 bTokOdx+Wx/c+E7f9SE1xy7QbZ/52oJKTA7jS7Q7qGEoo67N1ty4c49H2hGXiRbkmtWs gYtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689250995; x=1689855795; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KfgGwC6OQ1VQH6VfXv/s/6WQtbuBLu+ynhFeWV7RfAA=; b=amA9RNA9Q3pQIolrZyz+cmlyhW1Kfepynsvd+yOqwhBL56it5Adm69wG64X596Pxvo elnH5pTgslDl4LU6EsYv2Qf3PPSpTa8zPFSDgSadv7x2WVLY0P7SLMHpzOS5nMjvV0hu 1rZVvdREedkZUAwVCHdN+xQia0RECcHg2/Dbu3IqIoFdfJ5ImqDyUIhSYy2wVcUzvZ4L AcY9z647nzh/tdXr+drC4YaAaKRzGTJl1RYH8GvwLdqHXXmkertnn70vjttQSSPT73B7 uupioFiSvdDSEdYiKoOAxcoIyOCz/D75B5+qjFYARroSaahyo5Y+vUtkePbL2c1Uqhr+ TGVw== X-Gm-Message-State: ABy/qLYJN1FlNKS7VaToP8g9vL7iJc/kWQ/E2PXx7wHqS0s3jUDi1tv5 v11obEDkR4HYDPNIfbqCh8fv298R9DwrUhWYHko= X-Google-Smtp-Source: APBJJlGGNvBcwlmBuTIc/Go0wk55nEwR522Z76w0yl+rfT2KtXTR0A2B9DAE3r95I6YUpX3AfUT8M+Sh41F244rRQpY= X-Received: by 2002:a05:6102:c02:b0:443:62fe:6f3b with SMTP id x2-20020a0561020c0200b0044362fe6f3bmr534215vss.0.1689250994668; Thu, 13 Jul 2023 05:23:14 -0700 (PDT) MIME-Version: 1.0 References: <18e1c012-818c-44ee-ba95-c000860ac390@app.fastmail.com> In-Reply-To: Date: Thu, 13 Jul 2023 09:23:02 -0300 Message-ID: To: Brent Roose Cc: PHP Internals Content-Type: multipart/alternative; boundary="000000000000794a5a06005d6586" Subject: Re: [PHP-DEV] [VOTE] Interface Default Methods From: deleugyn@gmail.com (Deleu) --000000000000794a5a06005d6586 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jul 13, 2023 at 8:46=E2=80=AFAM Brent Roose via internals < internals@lists.php.net> wrote: > I want to pitch in, agreeing with Larry's message here. > > - There are multiple real life use cases where the combo trait/interface > could be replaced by interface default methods > - Several modern language apply the technique in one form or another, so > it's already proven to be valuable > - There are a multitude of userland devs who'd benefit from this feature > - The only argument I've heard against this RFC is "it goes against my > definition of what an interface should be". I was also thought that same > definition, and I also had to unlearn it. Just like I had to unlearn the > "only one return per method rule" we were taught in college > > Brent > This was a valuable message for me. It helps me pinpoint my frustration with this RFC. - We have userland desire - There's prior art in other languages - It's already "doable" (Interface+Trait) - It adds a ton of convenience. - I have not seen any negative opinion about the implementation or impact on the php-src source code. What we're left with is either: - Let's have this but not on PHP 8.3 due to time constraint - Let's not have this If it's a time constraint, it would be good to hear more from folks that voted no so that it can light up hope. If it's just because voters don't want to let us have this then it's really just frustrating. --000000000000794a5a06005d6586--