Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120608 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 86662 invoked from network); 16 Jun 2023 23:29:02 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Jun 2023 23:29:02 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E2404180089 for ; Fri, 16 Jun 2023 16:29:01 -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-vk1-f170.google.com (mail-vk1-f170.google.com [209.85.221.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 16 Jun 2023 16:28:58 -0700 (PDT) Received: by mail-vk1-f170.google.com with SMTP id 71dfb90a1353d-46e92a905bcso486086e0c.0 for ; Fri, 16 Jun 2023 16:28:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686958137; x=1689550137; h=content-transfer-encoding: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=kM2jlsp4kpWeId37SLJhDGEvgDrIF1gklK6Y+OA19jw=; b=caMYtnGyL+eFfbw3xz4oyTZt3zzPlVweyicpvwuqAsw4zIhQdHbS/y60wrqZ0GnV6c vEl/LNWgOHy88j7sXG36Rkindcm8rbTmExD1keUiO6HQxzLxpq0p6NBbEdeAc//cAlub qCI/0XMjkEc+41El6iKo4+y+b8MkM0aqOFk6c7jyGJS+7d79Z6NyaxtSazthSjT9Ritq 9MG64P8lmqXOLrXM9Yqm+ZtYJ7jn40SOuq+AQrTzoVT+H7y6bjNUbvgJ7OLGUiPBZFuG zoyuflIPVMFPiKKj0pmeZkQ4M7s8NJ2LBBhcJPrv/1QY7n/kPKSkEjYbc5hVozrOZf5/ ldvA== X-Gm-Message-State: AC+VfDymDRyYncdDxoR+Q6K0Y+aGSUdCJW9H0lSfbsLE3nuV7Ys8BXx4 TLiEgQ8HiiikoNYogv3dundvGYQFJugy+f/JgLc= X-Google-Smtp-Source: ACHHUZ4eK6OU3ghmD8GGsC6FOW/6a2ysTdnW7s8YGI8085aSkx3TtVEQ1XjbCtqfXbQJNIRT7d33Pni3qQs6cBkVLpk= X-Received: by 2002:a1f:43c8:0:b0:471:24cd:333b with SMTP id q191-20020a1f43c8000000b0047124cd333bmr485390vka.10.1686958137481; Fri, 16 Jun 2023 16:28:57 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 16 Jun 2023 17:28:41 -0600 Message-ID: To: Levi Morrison Cc: Ilija Tovilo , PHP internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Interface Default Methods From: levim@php.net (Levi Morrison) On Thu, Jun 15, 2023 at 5:41=E2=80=AFPM Levi Morrison via internals wrote: > > On Thu, Jun 15, 2023 at 3:37=E2=80=AFPM Ilija Tovilo wrote: > > > I am moving my RFC for interface default methods to discussion: > > > https://wiki.php.net/rfc/interface-default-methods. > > > > The RFC doesn't mention default implementations for static methods. > > I'm not sure there's a use case but it might make sense to explicitly > > mention whether they are supported. > > Interesting point. I sometimes forget that `static` is allowed in > interfaces. When I rebase the branch, I'll check it out. I assume it > works at a technical level without issues. If that's true, then absent > further evidence, I would say to allow it. I have rebased my branch on the latest master, and added a test case that default methods work with static methods on interfaces. They do. If you can think of any interesting test cases to add in that space, feel free. PR: https://github.com/php/php-src/pull/11467