Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120630 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 24037 invoked from network); 20 Jun 2023 03:10:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Jun 2023 03:10:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 9F422180089 for ; Mon, 19 Jun 2023 20:10:22 -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, 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-vs1-f50.google.com (mail-vs1-f50.google.com [209.85.217.50]) (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 ; Mon, 19 Jun 2023 20:10:22 -0700 (PDT) Received: by mail-vs1-f50.google.com with SMTP id ada2fe7eead31-440b5998e47so503608137.3 for ; Mon, 19 Jun 2023 20:10:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687230621; x=1689822621; 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=VkYA6RxXKQf6UIN3PDFBRNW09Uo0knAKnOn/qkaJ2yo=; b=loKIiiob1P6sZyjKemdRjROaFQJkZ2k77NDGF2jyD5mVTc2oUyQExaBejVdbwY639f kaSkNQ35jtCWao4RQJN8uOvTTnowEW86kmo3Y+T6O4Oa0EjmYHnYsvpd7eJYwo4zwUBn AJYrWqzPrf7+txidsPuIWcploaGJAPZlQTvcweZWlrlY5UmIgo90fpJtrDwFFxez1mHv KncGFP1T885fhV0gptlMk3TtJ9U9xiH7/Sm0MwAVOTyKkWToVcemD6b4B6coFAx3Ql0X TUq6qdBgQUdWblcA6uZqlDAw/NSsv2qv+T3nwiBCQtPX9rDOM/KI6PFw2bjGMVjbKdc2 OiNw== X-Gm-Message-State: AC+VfDyLb7qFoHWXQcVqh8+a+D7BvoEkmFklmhg42r/5RJiVIp4W/lj9 uoXJ/oap7y9wbg280TKy4m8Aly4AQQqShtc11Po= X-Google-Smtp-Source: ACHHUZ51TbfS0eog/7t4RPbR/GLLvPPoXCt+HBmGdzuaZdHkPY1OaQ72g8JoX49/Qcbwl11TOvub+nVNUuiVmci7TF4= X-Received: by 2002:a05:6102:242:b0:43c:b0d:fff5 with SMTP id a2-20020a056102024200b0043c0b0dfff5mr3179103vsq.7.1687230621268; Mon, 19 Jun 2023 20:10:21 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 19 Jun 2023 21:10:05 -0600 Message-ID: To: David Gebler Cc: Rowan Tommins , internals@lists.php.net Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC] Interface Default Methods From: levim@php.net (Levi Morrison) > I like the idea of this RFC - in fact it's one which has been near top of > my wishlist for PHP language features for a long time - but I think this is > an issue with the proposed implementation which at the very least warrants > highlighting and discussion. I understand your concern but personally believe it's overblown. This problem already exists with abstract classes, but doesn't seem to be that much of an issue in practice. I hope static analysis can fill the gap here, but don't think these checks are necessary to ship this feature.