Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120594 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 54112 invoked from network); 15 Jun 2023 15:48:34 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Jun 2023 15:48:34 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E5D34180511 for ; Thu, 15 Jun 2023 08:48:33 -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=-0.2 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,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-wr1-f47.google.com (mail-wr1-f47.google.com [209.85.221.47]) (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 08:48:33 -0700 (PDT) Received: by mail-wr1-f47.google.com with SMTP id ffacd0b85a97d-3090d3e9c92so7778456f8f.2 for ; Thu, 15 Jun 2023 08:48:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=datadoghq.com; s=google; t=1686844112; x=1689436112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=P+lpPfVdX4oA4+YvOMMJo6Bp5v9/fT5/+XG8hBl5h5o=; b=QDMvlYpMeFpFg284ZAPgskG8H5/lcqiTny7HTc7GJMd/Bh1FIUA8U6js1jmFhKDu8V REPuIMlk3St/++s8pYTfnosCdTQlg+OpF4Q1ZyKwnVadSxCqMMKPpfEdUIryh93EGAHY JWeSBns0rjG2xbsRa2aCdoZV7A4DDukXzcElo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686844112; x=1689436112; 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=P+lpPfVdX4oA4+YvOMMJo6Bp5v9/fT5/+XG8hBl5h5o=; b=L4NlDAHv66Tv7LAXimk5sW6ojMcPjZOBkxXzy1to1iUEWQKSOoifD370Q6uC/gGkf8 iNUW2GZVhTCSU/LVtS0JilBvqcMi/wJ8NBXyRP7ZR9fOvqQufB6rE5KfJmq4o8UphmjF v9r1QYG6NEfLWoS/z2UxJxFIEOwc7CS54RpT6d7/uQ+ZZ33MDjfAU4WDZy7M2X6GQNG/ EkY2kPWtnKcqjJsBk1tSkMY4MnXcuwFAYm9tJPDjKujvUF1llcAnSKXKvdL4y+w7AWWe zNcJURt8N3OYZR6NBjvFcUn+pIMfMiD/Yv7ua8/DUBidJf7xr8ZWbhP/fqXoUtp8NQtA Gv2w== X-Gm-Message-State: AC+VfDwpSummzCAAmtkBc6wWzvB3ObtSYjucY1eqrkyY5uK1owj8JWyy 6y3le4y59DopMuP6SIjQpr68KVSiSeu/hhNCTgmhFIUppKCzKX1kEt2EHhth X-Google-Smtp-Source: ACHHUZ6b/QLrsuqid+GLdy4tqPRDSrF8Hp/DWkoaJv4nC2M9dradK0A0qIKm6HQRWdefhHlPPtcK2Rf82uPnVRvZ3jI= X-Received: by 2002:a5d:4e50:0:b0:311:1390:7b55 with SMTP id r16-20020a5d4e50000000b0031113907b55mr2249533wrt.68.1686844112122; Thu, 15 Jun 2023 08:48:32 -0700 (PDT) MIME-Version: 1.0 References: <648AAE1D.9070805@adviesenzo.nl> <648B30B5.50705@adviesenzo.nl> In-Reply-To: <648B30B5.50705@adviesenzo.nl> Reply-To: Levi Morrison Date: Thu, 15 Jun 2023 09:48:20 -0600 Message-ID: To: Juliette Reinders Folmer Cc: internals@lists.php.net Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC] Interface Default Methods From: internals@lists.php.net ("Levi Morrison via internals") > I still believe this information should be added to the RFC as the risk > of adding new methods to an interface which collide with existing > methods in implementations of that interface is very real, though I > agree with Deleu that this BC impact is not so much of the RFC, but of > what can happen once the RFC would be accepted. Juliette, it's in the RFC under the second bullet point here: https://wiki.php.net/rfc/interface-default-methods#backward_incompatible_changes. Is there something specific you'd like added there?