Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120599 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 74047 invoked from network); 15 Jun 2023 19:31:29 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Jun 2023 19:31:29 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id C122A180382 for ; Thu, 15 Jun 2023 12:31:28 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,FREEMAIL_REPLY, 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-yb1-f173.google.com (mail-yb1-f173.google.com [209.85.219.173]) (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 ; Thu, 15 Jun 2023 12:31:25 -0700 (PDT) Received: by mail-yb1-f173.google.com with SMTP id 3f1490d57ef6-bd790f26791so2127370276.1 for ; Thu, 15 Jun 2023 12:31:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686857484; x=1689449484; h=mime-version:subject:references:in-reply-to:message-id:cc:to:from :date:from:to:cc:subject:date:message-id:reply-to; bh=vRwiWa+Xte10leSyFFyfVtSuxeV5TG3riXnhNjHp3rE=; b=JOXP2lrF0BrKkwaDHMpDb+5+wv5XPCyzth0Fx586iFCna61TGNTXUD9KZPOQEcwwcy 3dZY3479l8V7mnMBSMYThfJTpTGF3XJASLRs1Itarj0gkKUMSIzJzOn923DFK5PTg1Q7 4LOx33imYdqEqfCfh/dto+/lydkDe6U46EJzjm8O9bx3pCl03fQzj8NvJ5QfTRJbXwE5 A5CNhu4+cpMBt8mHjttxDzCwzFvWeE2cn/UcCLAOhXGbcsFwGqXKsePt4f/rkSvAHrwF tErHcjFxtnXcYiRkdEdo2CwL5HU4F2ZV+H5aXeDzk9SsuAuciVhT5qmakdEU4VoQji6D RqMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686857484; x=1689449484; h=mime-version:subject:references:in-reply-to:message-id:cc:to:from :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=vRwiWa+Xte10leSyFFyfVtSuxeV5TG3riXnhNjHp3rE=; b=WxoJwyuYl1asHxujFJZRAbelyJSITWPMgVXCXuOQSf2kFMfjAZUd1sF61gUeAxCJ6u I/M45lA7OmRz3gX5Z/zGoaFusNEfE0QK7a2nzaamZFEev4jbkoD1vx+atvFkXSUu6Gdl ovSoQGQ2RwktSkOASNn996MpcgW/eW4TcvE/2JZ3L8GrXwYnriOYvkorZnsfMrFCLhB+ OH7lwTcHrRxcAT2jBrs8GX/lZh84hcAm2NbFPizu82RodUozPyC4jGdzUs+yoK9NHwJs /flFm5tck/F9XVOq6G6545sJ+8abuD/27uid2to2XFp7bZHhDxZ1UglHWPPhwS9t/KPf 62qg== X-Gm-Message-State: AC+VfDxua8rXFrt6UPzaS2emMyuEhaWltZw46MeJiaUbw1BE+PrjEb7+ /cxff8E5zJzNBXWirYdWs0lHoYZwN9c= X-Google-Smtp-Source: ACHHUZ4bRmSDN3W8L9hesegAniQzpq+RPApkaW7AsyrkKlqKDx1nkpafZMH/PAIH1Jnc+NeVR2spCA== X-Received: by 2002:a25:8012:0:b0:bc6:7079:563d with SMTP id m18-20020a258012000000b00bc67079563dmr5347915ybk.45.1686857484358; Thu, 15 Jun 2023 12:31:24 -0700 (PDT) Received: from [2603:9000:a900:6262:70dd:f14e:f87f:0] (2603-9000-a900-6262-0846-0f59-ffc4-29f3.inf6.spectrum.com. [2603:9000:a900:6262:846:f59:ffc4:29f3]) by smtp.gmail.com with ESMTPSA id o124-20020a254182000000b00bd74eb95db3sm1085999yba.16.2023.06.15.12.31.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Jun 2023 12:31:24 -0700 (PDT) Date: Thu, 15 Jun 2023 15:31:23 -0400 To: internals@lists.php.net Cc: Deleu Message-ID: <1620a733-756f-48eb-8dd3-52458d98d6d4@Canary> In-Reply-To: References: <648AAE1D.9070805@adviesenzo.nl> <648B30B5.50705@adviesenzo.nl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="648b670b_643c9869_1b46" Subject: Re: [PHP-DEV] [RFC] Interface Default Methods From: michael.babker@gmail.com (Michael Babker) --648b670b_643c9869_1b46 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > On Thursday, Jun 15, 2023 at 12:01 PM, Deleu wrote: > > One can argue that this change might make it so that users start > considering adding methods with default implementation as > not-so-much-a-bc-break and do so without bumping a major version, in wh= ich > case this R=46C could be said to =22open the door for some users to sta= rt > introducing BC-breaks without bumping major version=22 because they con= sider > it a much smaller BC break, but it can't be said to open the possibilit= y. At this point, though, how different is the impact from this type of B/C = break from the B/C break that already occurs when new methods are added t= o non-final classes where a subclass used a different signature and isn=E2= =80=99t compatible with the new addition=3F - Michael --648b670b_643c9869_1b46--